wst/components/sse/M5/milestone_plan.xml

<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="../../../../development/milestone_plans/stylesheets/milestone-bulletList.xsl"?>

<plan xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:noNamespaceSchemaLocation="../../../../development/milestone_plans/milestonePlan.xsd">
	<component name="sse" subproject="wst">
		<description>Milestone planning for SSE Component</description>
		<milestone name="M5">
			<title>M5 Plan - updated 3/13/2005</title>
			<category name="Design for Platform Use">
				<item priority="medium" status="in-progress">
					<description>
						Continue Document Designs, API, JUnit tests, and
						Performance Tests
					</description>
					<detail>
						Create component.xml files, create JUnit tests,
						verify performance runs.
						<ul>
							<li>
								Editor overview, primarily extended
								configuration, editor IDs, etc.
							</li>
							<li>
								Model overview, StructuredDocument vs.
								IDocument, ModelManager, etc.
							</li>
							<li>Content Type Describers, encoding.</li>
						</ul>
					</detail>
				</item>
				<item priority="medium" status="in-progress">
					<description>
						Continue refactoring to improve separation of
						components
					</description>
				</item>
			</category>
			<category name="New Features">
				<item priority="medium" status="investigate">
					<description>
						Use Base Spell Checking with Validation
						Framework
					</description>
				</item>
				<item priority="low" status="investigate">
					<description>
						Investigate Semantic Highlighting
					</description>
					<detail>
						This may take some experimenting to find best
						solution to do both syntax highlighting (using
						line event callback) and semantic highlighting
						based on DOM (using presentation reconciler).
					</detail>
				</item>
			</category>
			<category name="Eclipse Base API Compliance">
				<item priority="medium" status="in-progress">
					<description>
						Reduce Editor/Viewer subclassing
					</description>
					<detail>
						In general, further reduce specialized
						subclassing/overriding to only what's necessary.
					</detail>
				</item>
				<item priority="medium" status="in-progress">
					<description>
						Move closer to IDocument compliance.
					</description>
					<detail>
						In general, further reduce specialized
						subclassing/overriding to only what's necessary.
						Such as, no separate structured document
						listeners, ensure meeting content type specs,
						document partitioner specs, etc.
					</detail>
				</item>
				<item priority="medium" status="in-progress">
					<description>
						Improve Document, Position, Model
						synchronization
					</description>
					<detail>
						Requires some APIs move "down" to
						JobSafeDocument, and requires internal
						notification cycle to gaurd against "call outs"
						during locked code.
					</detail>
				</item>
				<item priority="medium" status="investigate">
					<description>
						Conform to base Eclipse Selection
						management/providers
					</description>
					<detail>
						We currently have a ViewerSelectionManager which
						we want to be "internal" and investigate if we
						can provide same function via the base Eclipse
						Selection and SelectionProvider API.
					</detail>
				</item>
			</category>
			<category name="Eclipse Base Parity">
				<item priority="medium">
					<description>
						Move to new Eclipse base Common Undo Stack
						Infrastructure
					</description>
				</item>

				<item priority="medium" status="in-progress">
					<description>Folding</description>
					<detail>
						Believed done except requires fix for
						document/model synchronization.
					</detail>
					<developer name="amywu@us.ibm.com" />
				</item>
				<item priority="medium" status="in-progress">
					<description>Task Tags from contents</description>
				</item>
			</category>
			<category name="Performance">
				<item priority="low" status="investigate">
					<description>
						Improve partitioner's performance.
					</description>
					<detail>
						Use separate data structure. Investigate
						generated JavaCC parser on JFlex tokens. This
						should have a notable effect on the speed on the
						scrolling speed in the editor.
					</detail>
					<developer name="nitind@us.ibm.com" />
				</item>

				<item priority="low" status="investigate">
					<description>
						Move to latest version of JFlex
					</description>
					<detail>
						This may help the scrolling speed in the editor.
					</detail>
					<developer name="nitind@us.ibm.com" />
				</item>
				<item priority="low" status="investigate">
					<description>
						Investigate numerous model and document
						implementation improvements
					</description>
					<detail>
						<ul>
							<li>
								Add (transparent) model caching (not
								just sharing)
							</li>

							<li>
								Limit number of adapter notifications
								sent (and/or optimize 2000 peer children
								case). This may help speed up the
								formatter performance.
							</li>

							<li>
								Fix document to model thread
								(notification) synchronization
							</li>

							<li>
								Fix "stop/resume" notifications (now
								rewrite modes)
							</li>

							<li>
								Investigate improved text store, better
								suited to DOM editing
							</li>

							<li>
								Investigate Add "compare" methods, so
								less frequent 'gets' are needed
							</li>
						</ul>
					</detail>

				</item>
				<item priority="low">
					<description>
						Improve "adapt on create" design and
						implementation.
					</description>
				</item>
				<item priority="low">
					<description>
						Improve "read-only" design
					</description>
				</item>
				<item priority="medium">
					<description>
						Improve formatter performance
					</description>
					<detail>
						We believe the main problem is excessive
						notifications for formatting large areas of
						text. We should be able to know that formatting
						is happening, and perform all edits at once with
						minimal notifications of elements changing,
						especially since it's "only" whitespace being
						changed.
					</detail>
				</item>
				<item priority="low">
					<description>
						Investigate "sparse model" design for memory
						savings
					</description>
					<detail>
						A possible improvement may be to perform a
						"coarse" parsing the first time though. That is,
						only parse StructurdDocumentRegions, then only
						provide finer details of those regions upon
						request. This is more along the lines of "pay as
						you go", which seems to be the overall direction
						of Eclipse.
					</detail>
				</item>
			</category>
			<category name="Quality">
				<item priority="high" status="in-progress" helpWanted="true">
					<description>Define JUnit testcases for internal provisional API.</description>
					<developer name="david_williams@us.ibm.com"/>
				</item>
				<item priority="medium" status="in-progress" helpWanted="true">
					<description>Define or enhance non-API JUnit testcases.</description>
					<developer name="david_williams@us.ibm.com"/>
				</item>
				<item priority="high" status="investigate" helpWanted="true">
					<description>Write on-line documentation.</description>
					<developer name="david_williams@us.ibm.com"/>
				</item>
			</category>
		</milestone>
	</component>
</plan>