wst/components/sse/M5/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="M5">
                        <title>M5 Plan (initial Rough Draft)</title>
                        <category name="New Features">
                                <item priority="low" status="investigate"
                                        helpWanted="true">
                                        <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 parity">
                                <item priority="medium">
                                        <description>
                                                Move to new Eclipse base Common Undo Stack
                                        </description>
                                </item>
                        </category>
                        <category name="Performance">
                                <item priority="medium">
                                        <description>
                                                Improve "adapt on create" design and
                                                implementation.
                                        </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>