These API specification versions may be used to indicate that a module
requires a certain API feature in order to function. For example, if you
see here a feature you need which is labelled 1.20, your
manifest should contain in its main attributes the line:

Swing NavigationFilters implemented on top of the Caret API. Caret API caller may describe the operation which causes
the caret to be moved, so that filters and caret listeners can react on specific action groups.

A boilerplate NavigationFilter is provided, that supports chaining of filters on the caret

Apr 16 '13; API spec. version: 1.79; made by: mkristofic; issues:
#217163
Typing Hooks Camel Case SPI is addition to Typing Hooks. it allows interception of various key events
that are processed in the editor. The SPI is a replacement for
subclassing editor actions such as RemoveWordNextAction, PreviousCamelCasePosition, etc.

May 15 '09; API spec. version: 1.11; affected top-level classes: DialogBinding; made by: dbalek; issues:
#163769DialogBinding allows for content of some text component to be virtually placed
to the given offset inside of a file or document. This way, the necessary context is
provided for code completion and similar features to work in any text component.

Sep 13 '07; API spec. version: 1.5; made by: vstejskal; issues:
#107107
The HighlightAttributeValue allows specifying highlights
with attributes, which value is lazily evaluated at the time when
the attrbute is used. For example when specifying tooltips.

Jun 7 '07; API spec. version: 1.4; made by: mmetelka; issues:
#103235
The EditorRegistry allows to get focused and last focused text component
and list of all registered components and it allows to listen for currently focused
component and changes of documents in it.