sse M9 Milestone planning for SSE Component |
|  |
1.0M9 Plan - updated 9/27/2005 |
 | Design for Platform Use Provide API to embed source page editor in multipage editors and improve integration with the Eclipse platform Continue refactoring to improve separation of components [medium]- Transition IModelManager to using a connect/disconnect pattern with IPaths and InputStreams, and provide an I(Structured)DocumentManager for managing structured documents in the absence of structured models. [medium]
- Declare supported API for StructuredDocument/TextRegions/Parsers [medium]
- Transition ModelHandlers to ModelFactorys [medium]
- Create a NodeAdapterFactoryManager and disable/remove current adapter factory extension point [medium]
- Document IEditorPart adapter handling recommendations [medium]
- Code folding [medium]
 - Remove encoding mementos and document alternate methods using content describers [low]
- Correct partitioner implementations and usages by StructuredDocument implementations [low]
|
|
 | Provide APIs to extend our source editor Document and finalize PropertySheetConfiguration [high] Document and finalize ContentOutlineConfiguration [high] Plan what to do with Text Tools, preference page IDs, and other current usages [medium] Eliminate StructuredTextEditor subclasses and switch to plugin action contributions [high] - Document APIs for Validation, both Source and Batch [high]
- Make API out of our Highlighting scheme, after investigating avenues with TextPresentation for semantic highlighting [medium]
- Clarify and define Formatting API [low]
- Provide extensibility in Content Assist [low]
 - Clean up Preferences [low]
 - Find where we're violating our own APIs and clean them up [low]
|
|
 | Performance Improve memory usage, performance, and thread safety- Improve Thread safety by abandoning the use of of IStructuredDocumentRegion.getNextNode for iteration; use IStructuredDocument.getNodes(offset, length) instead [medium]
Investigate numerous model and document implementation improvements [low] - Improve "adapt on create" design and implementation. [low]
- Improve "read-only" design [low]
- Improve formatter performance [medium]
 - Investigate "sparse model" design for memory savings [low]
 - Redesign StructuredDocument/TextRegions/Parsers to shrink memory usage [medium]
|
|
 | Other functionality- Document Drag and Drop abilities [medium]

|
|
 | Quality Continue to Document Designs and API, create JUnit and Performance Tests [medium] Define and enhance JUnit testcases. [medium] Write on-line documentation. [medium]
|
|
Legend |
 | item is under development. |  | item is under investigation. |
 | item is finished. |  | help wanted |
 | item is deferred. |  | new |