wst/components/sse/M3/milestone_plan.xml

<?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 Core, UI, and Tools
		</description>
		<milestone name="M3">
			<title>
				M3 Plan Status: under development and
				review - updated 2005-2-24
			</title>
			<category name="Design for Platform Use">
				<item priority="high" status="in-progress">
					<description>
						Document Designs, API, JUnit tests, and Performance Tests
					</description>
					<detail>
						During M3 we'll focus primarily on core (model)
						Designs and APIs.
					</detail>
				</item>
				<item priority="medium" status="in-progress">
					<description>
						Continue refactoring to improve separation of
						components
					</description>
				</item>
			</category>
			<category name="Eclipse Base API compliance">
				<item priority="medium" status="done">
					<description>
						Fix Editor to handle any IDocument
					</description>
					<detail>
						In general, further reduce specialized
						subclassing/overriding to only what's necessary.
					</detail>
				</item>
				<item priority="high" 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>
			</category>
			<category name="Eclipse base parity">
				<item priority="high" status="in-progress">
					<description>Folding</description>
					<developer name="amywu@us.ibm.com"/>
				</item>
				<item priority="high" status="done">
					<description>
						Preference Re-organization
					</description>
				</item>
			</category>
			<category name="Performance">
				<item priority="medium" status="deferred">
					<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="medium" status="deferred">
					<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>
			</category>
		</milestone>
		<milestone name="M4">
			<title>
				M4 Plan (initial Rough Draft - last updated 2005-1-11 -
				to be completed at end of M3)
			</title>
			<category name="New Features">
				<item priority="high">
					<description>Task Tags from contents</description>
				</item>
				<item priority="high">
					<description>Spell Checking</description>
				</item>
			</category>
			<category name="Eclipse base parity">
				<item priority="high">
					<description>
						Move to new Eclipse base Common Undo Stack
					</description>
				</item>
			</category>
			<category name="Performance">
				<item priority="medium">
					<description>
						Improve "adapt on create" design
					</description>
				</item>
				<item priority="medium">
					<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="medium">
					<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>
		</milestone>
		
	</component>
</plan>