Hello,
A draft on the editor configuration extension point is ready for review. Below is an overview of the document. I should note that the contentoutlineconfiguration and propertysheetconfiguration classes are still in the process of being cleaned up, but StructuredTextViewerConfiguration and its subclasses are ready to rock. All those classes are still currently under a provisional package, but they will be moved out of provisional shortly (eta: next week's ibuild) Code changes are already in CVS, and editors in WTP will be/have been updated in response to the changes. Heads up to anyone using internal SSE api (content assist, reconciler, line style provider, viewer configuration), you may need to do some reacting. A small migration guide is also referenced in the design document.
Enjoy.
Overview:
| 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:
|
Please read the rest of the document here:
http://eclipse.org/webtools/wst/components/sse/designs/EditorConfiguration.html
Comments, suggestions? Please add to bug 109026
https://bugs.eclipse.org/bugs/show_bug.cgi?id=109026
______________________________
Amy Wu
Structured Source Editor
919.254.0299, T/L 444.0299
[EMAIL PROTECTED]
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
