One main goal of
the Structured Source editing framework is to provide a way for clients
to extend the Structured Text Editor without having to subclass the editor.
Part of this goal is achieved through the editor configuration extension
point. The editor configuration extension point allows clients to customize
the Structured Text Editor for different/new content types.
The Structured Text editor is designed to
handle different types of "structured" content types as input,
such as XML, HTML, JSP, CSS. This includes the ability to change content
types on-the-fly. For example, editing an HTML document, then deciding
to change it to JSP by performing Save As.. *.jsp. The different types
of configurations clients can contribute include:
- Outline view configuration - configure behaviour
in the outline view (elements to display, menu items, etc)
- Properties view configuration - configure
behaviour in the properties view (properties to display, menu items, etc)
- Structured text viewer configuration - configure
behaviour in the editor (content assist, syntax highlighting, hyperlink
navigation, etc)
Through an extension
point, clients can declare their configuration and the associated content
type or editor id. |