platform-text-home/3.1/previous_plans.html
Parent Directory
| 
Revision Log
Revision 1.15 -
(download)
(as text)
(annotate)
Mon May 2 15:00:08 2005 UTC (4 years, 6 months ago) by dmegert
Branch: MAIN
Changes since 1.14: +12 -0 lines
Mon May 2 15:00:08 2005 UTC (4 years, 6 months ago) by dmegert
Branch: MAIN
Changes since 1.14: +12 -0 lines
Added previous milestone test plans
<!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]"> <title>Platform Text Component</title> <link rel="stylesheet" href="http://dev.eclipse.org/default_style.css" type="text/css"> </head> <body text="#000000" bgcolor="#FFFFFF"> <table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" > <tr> <td ALIGN=LEFT VALIGN=TOP COLSPAN="2" WIDTH="100%" BGCOLOR="#0080C0"><b><font face="Arial,Helvetica"><font color="#FFFFFF">3.1 Development Effort - Previous Milestone Plans</font></font></b></td> </tr> <tr> <td WIDTH="100%"> <h3><a name="Milestone_Planning"></a>Milestone M6 Plan</h3> <h4><img src="http://www.eclipse.org/images/Adarrow.gif" nosave="" border="0" height="16" width="16" align="top"> Top five items</h4> <ul> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> continue with J2SE 5.0 support (<a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/r3_1/j2se50/Status.html">JDT UI's overall status</a>)</li> <li><font class="indexsub" color="#8080ff">[>3.1]</font> progress in consolidating the platform</li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> provide NLS tooling for new Platform Core's new message bundle approach</li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> finalize existing 3.1 APIs (M6 is API freeze)</li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> performance</li> </ul> <h4><img src="http://www.eclipse.org/images/Adarrow.gif" nosave="" border="0" height="16" width="16" align="top"> Committed items</h4> <ul> <li> <h5>(<img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10">) Cross-team issues</h5> <ul> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> resolve missing performance test fingerprints problem</li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> adopt global operation history</li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> help push down formatter to JDT Core</li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> apply mixed indent patch for fomatter together with JDT Core</li> <li><font class="indexsub" color="#8080ff">[>3.1]</font> (provide a compatibility layer for commands moved to LTK UI plug-in)<br> a hard-coded patch is ready but there should be support from the Platform for extension-point evolution.</li> </ul> </li><li> <h5>(<img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10">) J2SE 5.0 support (<a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/r3_1/j2se50/Status.html">JDT UI's overall status</a>)</h5> <ul> <li>(<img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10">) fix bugs introduced in M5 <ul> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> performance impact due to parameter guessing</li> <li><font class="indexsub" color="#8080ff">[3.1 M7]</font> improve accurracy of auto-boxing</li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> problems introduced by new projection caption support</li> </ul> </li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> improve content assist for generics (work together with David Audel / JDT Core): <ul> <li>better type parameter proposals</li> <li>better enum constant proposals</li> </ul> </li> <li> <font class="indexsub" color="#8080ff">[>3.1]</font> (provide new semantic highlightings)</li> <ul> <li>type bounds</li> <li>enums</li> <li>static imports</li> </ul> </ul> </li><li> <h5><font class="indexsub" color="#8080ff">[>3.1]</font> Platform consolidation</h5> <ul> <li>push down annotation navigation</li> <li>push down annotation hovers</li> <li>adopt and push down Quick Assist and Quick Fix infrastructure</li> <li>offer spelling checking in Text editor</li> <li>(move Occurrences annotation type definition and annotation specification down to ltk.ui or editors.ui)</li> <li>(push down annotation navigation)</li> </ul> </li><li> <h5><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> NLS tooling</h5> <ul> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> provide tooling for Platform Core's new message bundle approach</li> <ul> <li>provide new back-end for the NLS wizard that can write the new format</li> </ul> <li><font class="indexsub" color="#8080ff">[>3.1]</font> (improve Properties File editor)</li> <ul> <li>(ensure correct ISO-8859-1 encoding when writing a properties file)</li> </ul> </li> <li><font class="indexsub" color="#8080ff">[>3.1]</font> (improve Externalize Strings wizard) <ul> <li>(spell checking)</li> <li>(ensure correct ISO-8859-1 encoding when writing a properties file)</li> </ul> </li> </ul> </li><li> <h5><font class="indexsub" color="#8080ff">[3.1 M7]</font> (Code cleanup)</h5> <ul> <li>reference to AnnotationExpandHover in JavaExpandHover</li> <li>references to Search plug-in in PropertyKeyHyperlink</li> </ul> </li><li> <h5><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> R3.0.2 related work items</h5> <ul> <li>testing</li> <li>bug verification</li> <li>ship 3.0.2</li> </ul> </li><li> <h5><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> participate in writing an article for the JavaMagazin</h5> </li></ul> <h4><img src="http://www.eclipse.org/images/Adarrow.gif" nosave="" border="0" height="16" width="16" align="top"> Permanent items</h4> <ul> <li>bugzilla inbox tracking</li> <li>bug fixing</li> <li>increase correctness test coverage</li> </ul> <h4><img src="http://www.eclipse.org/images/Adarrow.gif" nosave="" border="0" height="16" width="16" align="top"> Proposed items</h4> <ul> <li><font class="indexsub" color="#8080ff">[>3.1]</font> add UI for Word Completion similar to code assist</li> <li><font class="indexsub" color="#8080ff">[>3.1]</font> add new <code>org.eclipse.ltk.ui</code> plug-in to release<br> <b>Note:</b> This item depends on the above mentioned cross team-issue</li> <li> <h5> <font class="indexsub" color="#8080ff">[>3.1]</font> (RCP)</h5> <ul> <li>add support for annotation presentation and navigation</li> <li>investigate declaring <code>org.eclipse.resources</code> optional for <code>org.eclipse.core.filebuffers</code></li> <li>provide an example RCP text editor application with the following features:<br> <ul> <li>open an external file</li> <li>open an untitled (new & empty) text file</li> <li>save</li> <li>spell checking</li> <li>quick fix to fix spelling problems</li> </ul> </li> </ul> </li> </ul> <h4><img src="http://www.eclipse.org/images/Adarrow.gif" nosave="" border="0" height="16" width="16" align="top"> Absences</h4> <ul> <li>Dani: 5 days vacation</li> <li>Tom: 5 days eclipseCon</li> <li>Tom: 5 days vacation</li> <li>2 public holidays</li> </ul> <h4><img src="http://www.eclipse.org/images/Adarrow.gif" nosave="" border="0" height="16" width="16" align="top"> Testing</h4> <ul> <li> The <a href="testing/testpass_M6.html">test plan</a> for the M6 test pass.</li> </ul> <!-----------------------------> <h3><a NAME="Milestone_Planning"></a>Milestone M5</h3> <h4><img src="http://www.eclipse.org/images/Adarrow.gif" nosave="" border="0" height="16" width="16" align="top"> Top five items</h4> <ul> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> start with J2SE 5.0 support (<a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/r3_1/j2se50/Status.html">JDT UI's overall status</a>)</li> <li>progress in consolidating the platform</li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> progress in improving NLS tooling</li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/progress.gif" nosave="" border="0" height="5" width="14" align="middle"> remove dependencies to internal code from other plug-ins</li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> R3.0.2 related work items</li> </ul> <h4><img src="http://www.eclipse.org/images/Adarrow.gif" nosave="" border="0" height="16" width="16" align="top"> Committed items</h4> <ul> <li> <h5><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/progress.gif" nosave="" border="0" height="5" width="14" align="middle"> Cross-team issues</h5> <ul> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/progress.gif" nosave="" border="0" height="5" width="14" align="middle"> resolve performance test problems</li> <li>participate in the action contribution dynamic team</li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/new.gif" nosave="" border="0" align="middle"> <img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/glass.gif" nosave="" border="0" height="10" width="10"> harmonize with potential global undo manager<br> The code is ready. We decided not to released it for M5 as it came close to the milestone. To be done at the beginning of M6. </li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/new.gif" nosave="" border="0" align="middle"> provide feedback for new Component Framework proposal (⇒ editor splitting)</li> <li>finish pushing down formatter to JDT Core</li> <li>provide a compatibility layer for commands moved to LTK UI plug-in:<br> a hard-coded patch is ready but there should be support from the Platform for extension-point evolution.</li> </ul> </li><li> <h5><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/progress.gif" nosave="" border="0" height="5" width="14" align="middle"> J2SE 5.0 support (<a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/r3_1/j2se50/Status.html">JDT UI's overall status</a>)</h5> <ul> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> investigate impact on the following JDT Text areas: <ul> <li>syntax highlighting</li> <li>content assist</li> <li>hovering</li> <li>comment formatting</li> <li>typing</li> <li>Java Outline page</li> <li>folding</li> <li>mark occurrences</li> </ul></li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> start to fix problems encountered in above investigation</li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> provide new templates</li> <li>provide new semantic highlightings</li> <ul> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> autoboxing</li> <li>type bounds</li> <li>enums</li> <li>static imports</li> </ul> </ul> </li><li> <h5>Platform consolidation</h5> <ul> <li>start adopting and pushing down Quick Assist and Quick Fix infrastructure</li> <li>push down annotation hovers</li> <li>offer spelling checking in Text editor</li> <li>(move Occurrences annotation type definition and annotation specification down to ltk.ui or editors.ui)</li> <li>(push down annotation navigation)</li> </ul> </li><li> <h5>(<img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10">) NLS tooling</h5> <ul> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> fix bugs reported in M4 test pass</li> <li>(<img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10">) improve Properties File editor <ul> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> improve detection of NLS accessor's resource bundle</li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> reduce false positives when navigating from Properties file editor to key references</li> <li>(ensure correct ISO-8859-1 encoding when writing a properties file)</li> </ul> </li> <li>(improve Externalize Strings wizard) <ul> <li>(spell checking)</li> <li>(ensure correct ISO-8859-1 encoding when writing a properties file)</li> </ul> </li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> investigate impact of Platform Core's new message bundle approach</li> </ul> </li><li> <h5><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/progress.gif" nosave="" border="0" height="5" width="14" align="middle"> Code cleanup</h5> <ul> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> identify dependencies to other plug-ins and request API if appropriate<br> The following API requests have been filed: <ul> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=79419">79419</a> [Preferences] Need a link component</li> <li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82256">82256</a> [Contributions] Need EditorPluginAction and ActionDescriptor.ATT_DEFINITION_ID as API<br> This will not be provided as there will be a new command story. We will keep the internal references until this is available. </li> </ul> </li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/progress.gif" nosave="" border="0" height="5" width="14" align="middle"> remove dependencies to internal code from other plug-ins</li> Most of them got fixed in M5. Besides the one mentioned above remaion for M6: <ul> <li>reference to AnnotationExpandHover in JavaExpandHover</li> <li>references to Search plug-in in PropertyKeyHyperlink</li> </ul> </ul> </li><li> <h5><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/ok.gif" nosave="" border="0" height="10" width="10"> R3.0.2 related work items</h5> Fixed two bugs. </li></ul> <h4><img src="http://www.eclipse.org/images/Adarrow.gif" nosave="" border="0" height="16" width="16" align="top"> Permanent items</h4> <ul> <li>bugzilla inbox tracking</li> <li>bug fixing</li> <li>increase correctness test coverage</li> </ul> <h4><img src="http://www.eclipse.org/images/Adarrow.gif" nosave="" border="0" height="16" width="16" align="top"> Proposed items</h4> <ul> <li>add new <code>org.eclipse.ltk.ui</code> plug-in to release<br> <b>Note:</b> This item depends on the above mentioned cross team-issue</li> <li>(Provide an example RCP text editor application with the following features:)<br> <ul> <li>open an external file</li> <li>open an untitled (new & empty) text file</li> <li>save</li> <li>spell checking</li> <li>quick fix to fix spelling problems</li> </ul> <b>Note:</b> it will require <code>org.eclipse.core.resources</code> plug-in </li> </ul> <h4><img src="http://www.eclipse.org/images/Adarrow.gif" nosave="" border="0" height="16" width="16" align="top"> Absences</h4> <ul> <li>Tom: 3 days vacation</li> </ul> <h4><img src="http://www.eclipse.org/images/Adarrow.gif" nosave="" border="0" height="16" width="16" align="top"> Testing</h4> <ul> <li> The <a href="testing/testpass_M5.html">test plan</a> for the M5 test pass.</li> </ul> <!-----------------------------> <h3><a NAME="Milestone_Planning"></a>Milestone M4</h3> <h4><img src="http://www.eclipse.org/images/Adarrow.gif" nosave="" border="0" height="16" width="16" align="top"> Original Plan</h4> <h4>Top Five</h4> <ul> <li> complete performance tests</li> <li>rework preferences</li> <li>finish file buffer operations</li> <li>progress in consolidating the platform</li> <li>improve NLS tooling</li> </ul> <h4>Committed items</h4> <h5>Cross-team issues</h5> <ul> <li> consolidate Ant, Platform UI, WTP, VE feedback and issues</li> <li> editor embedding and splitting <ul> <li>provide prototype for services architecture</li> <li>investigate how splitting would look like in a "component" world</li> </ul> </li> <li> participate in preferences dynamic team</li> <li> participate in the action contribution dynamic team</li> <li> work on and adapt to the new undo story</li> <li>migrate to the changed semantics of IPath</li> <li> finish pushing down formatter to JDT Core</li> </li> </ul> <h5>Testing</h5> <ul> <li> complete performance tests for the published <a href="performance_scenarios.html">set of scenarios</a></li> </ul> <h5>Component work</h5> <ul> <li>rework preferences <ul> <li>find all sharing scenarios (appearance, behavior, hovering, etc. ....)</li> <li>functional categorization</li> <li>check how WTP and other larger clients fit in</li> <li>implement different scenarios</li> <li>initiate review by usability team</li> </ul> </li> <li>finish file buffer operations <ul> <li>solve memory issues</li> <li>improve test coverage</li> <li>integrate with ltk core change architecture</li> <li>solve typing raise conditions</li> </ul> </li> <li>add document partitioning to StorageDocumentProvider <ul> <li>[investigate] exploit the existing filebuffer extension points</li> </ul> </li> <li>Java editor <ul> <li>initial color settings</li> <li>enable semantic highlighting by default</li> </ul> </li> <li>Default text editor <ul> <li>everything we push down while consolidating the platform needs to have a surfacing new function in the default text editor </li> <li>pushing down spell checking allows us to check whether the push down of the quick fix infrastructure is successful<br> </li> </ul> </li> </ul> <h5>Platform consolidation</h5> <ul> <li>create plug-in for 'Editing Source Scope' <ul> <li>move Occurrences annotation type definition and annotation specification down to ltk.ui or editors.ui</li> </ul> </li> <li>push down Ctrl-Click <ul> <li>[investigate] general resolution infrastructure</li> </ul> </li> <li>push down annotation navigation</li> <li>push down spell checking</li> <li>start adopting and pushing down Quick Fix infrastructure<br> </li> </ul> <h5>Code cleanup</h5> <ul> <li>fix IEditorHelper <ul> <li>use names that are self-describing and don't hamper further development</li> </ul> </li> <li>finish work on new functions not yet API<br> </li> </ul> <h5>NLS tooling</h5> <ul> <li>improve Properties File editor <ul> <li>fix reported syntax coloring issues</li> <li>navigate from selected key and value in a properties file to the location of usage in Java editor and Plug-in Manifest editor</li> <li>spell checking</li> <li>ensure correct ISO-8859-1 encoding when writing a properties file</li> </ul> </li> <li>support new nls features in Class file editor <ul> <li>coloring</li> <li>hovering</li> <li>navigation</li> </ul> </li> <li>improve Externalize Strings wizard <ul> <li>spell checking</li> <li>ensure correct ISO-8859-1 encoding when writing a properties file</li> </ul> </li> <li>investigate whether we can improve NLS tooling to support the string externalization approach used in TextOperationAction</li> </ul> <h4>Permanent items</h4> <ul> <li>bug fixing</li> <li>increase correctness test coverage</li> </ul> <h4>Proposed items</h4> <ul> <li> implement a SaveAs dialog that allows to save inside and outside of the workspace <ul> <li>involved parties: Platform UI, SWT, send patch to Platform UI</li> </ul> </li> <li>lazy loading of document setup participants</li> <li>allow for extending file buffers with custom implementations</li> <li>allow templates in the default text editor</li> <li>generalize and push down InformationDispatchAction</li> <li>generalize push down quick view support <ul> <li>Outline presentation control, AbstractInformationControl and related</li> </ul> </li> <li>[investigate] Consolidate SourceViewerInformationControl and all of its copies</li> <li>[investigate] allow for an outline mode in the default text editor <ul> <li>folding just based on indentation</li> <li>opens the way for using QuickOutline in the default text editor</li> </ul> <br> </li> </ul> <h4><img src="http://www.eclipse.org/images/Adarrow.gif" nosave="" border="0" height="16" width="16" align="top"> Finished</h4> <h5>Cross-team issues</h5> <ul> <li> consolidate Ant, Platform UI, WTP, VE feedback and issues</li> <li> editor embedding and splitting <ul> <li>provide prototype for services architecture</li> <li>investigate how splitting would look like in a "component" world</li> </ul> </li> <li>participate in preferences dynamic team</li> <li>migrate to the changed semantics of IPath</li> </ul> <h5>Testing</h5> <ul> <li> complete performance tests for the published <a href="performance_scenarios.html">set of scenarios</a></li> </ul> <h5>Component work</h5> <ul> <li>rework preferences <ul> <li>find all sharing scenarios (appearance, behavior, hovering, etc. ....)</li> <li>functional categorization</li> <li>check how WTP and other larger clients fit in</li> <li>implement different scenarios</li> <li>initiate review by usability team</li> </ul> </li> <li>finish file buffer operations <ul> <li>improve test coverage</li> </ul> </li> <li>Java editor <ul> <li>enable semantic highlighting by default</li> </ul> </li> </ul> <h5>Platform consolidation</h5> <ul> <li>create plug-in for 'Editing Source Scope'</li> <li>push down Ctrl-Click <ul> <li>[investigate] general resolution infrastructure</li> </ul> </li> </ul> <h5>Code cleanup</h5> <ul> <li>fix IEditorHelper <ul> <li>use names that are self-describing and don't hamper further development</li> </ul> </li> <li>finish work on new functions not yet API<br> </ul> <h5>NLS tooling</h5> <ul> <li>improve Properties File editor <ul> <li>fix reported syntax coloring issues</li> <li>navigate from selected key and value in a properties file to the location of usage in Java editor and Plug-in Manifest editor</li> <li>spell checking</li> </ul> </li> <li>support new nls features in Class file editor <ul> <li>coloring</li> <li>hovering</li> <li>navigation</li> </ul> </li> </ul> <h4><img src="http://www.eclipse.org/images/Adarrow.gif" nosave="" border="0" height="16" width="16" align="top"> Not Finished / Deferred to M5</h4> <h5>Cross-team issues</h5> <ul> <li>participate in the action contribution dynamic team</li> <li>finish pushing down formatter to JDT Core</li> <li>work on and adapt to the new undo story</li> </ul> <h5>Platform consolidation</h5> <ul> <li>(move Occurrences annotation type definition and annotation specification down to ltk.ui or editors.ui)</li> <li>(push down annotation navigation)</li> <li>push down spell checking</li> <li>start adopting and pushing down Quick Fix infrastructure<br> </li> </ul> <h5>NLS tooling</h5> <ul> <li>improve Properties File editor <ul> <li>ensure correct ISO-8859-1 encoding when writing a properties file</li> </ul> </li> <li>improve Externalize Strings wizard <ul> <li>spell checking</li> <li>ensure correct ISO-8859-1 encoding when writing a properties file</li> </ul> </li> </ul> <h4><img src="http://www.eclipse.org/images/Adarrow.gif" nosave="" border="0" height="16" width="16" align="top"> Deferred For Now</h4> <h5>Component work</h5> <ul> <li>finish file buffer operations <ul> <li>solve memory issues</li> <li>integrate with ltk core change architecture</li> <li>solve typing raise conditions</li> </ul> </li> <li>add document partitioning to StorageDocumentProvider <ul> <li>[investigate] exploit the existing filebuffer extension points</li> </ul> </li> <li>Java editor <ul> <li>initial color settings</li> </ul> </li> </ul> <h5>NLS tooling</h5> <ul> <li>investigate whether we can improve NLS tooling to support the string externalization approach used in TextOperationAction</li> </ul> <h5>Proposed items</h5> <ul> <li> implement a SaveAs dialog that allows to save inside and outside of the workspace <ul> <li>involved parties: Platform UI, SWT, send patch to Platform UI</li> </ul> </li> <li>lazy loading of document setup participants</li> <li>allow for extending file buffers with custom implementations</li> <li>allow templates in the default text editor</li> <li>generalize and push down InformationDispatchAction</li> <li>generalize push down quick view support <ul> <li>Outline presentation control, AbstractInformationControl and related</li> </ul> </li> <li>[investigate] Consolidate SourceViewerInformationControl and all of its copies</li> <li>[investigate] allow for an outline mode in the default text editor <ul> <li>folding just based on indentation</li> <li>opens the way for using QuickOutline in the default text editor</li> </ul> <br> </li> </ul> <h4><img src="http://www.eclipse.org/images/Adarrow.gif" nosave="" border="0" height="16" width="16" align="top"> Testing</h4> <ul> <li> The <a href="testing/testpass_M4.html">test plan</a> for the M4 test pass.</li> </ul> <!-----------------------------> <hr> <h3>Milestone M3</h3> <h4>Original Plan</h4> <h5>Committed items</h5> <ul> <li>performance <ul> <li> continue performance tests <ul> <li>reflect about scope and applicability of test results (annotate test cases accordingly)</li> <li>complete performance tests for the published <a href="performance_scenarios.html">set of scenarios</a></li> </ul> </li> <li> improve performance <ul> <li>e.g., new line at end of commented StyledText.java</li> </ul> </li> </ul> </li> <li>continue with file buffer issues as outlined in the 3.1 plan <ul> <li>adapt existing code to document rewrite sessions <ul> <li>improve formatting performance</li> </ul> </li> <li>simplify temporal suspension of document partitioners for performance reasons <ul> <li>investigate lazy document partitioners</li> </ul> </li> </ul> </li> <li>continue with encoding issues listed in the 3.1 plan <ul> <li>integrate the 'Change Encoding...' action with the status editor shown in case of encoding errors</li> <li>re-establish encoding support for external files</li> <li>react to resource encoding changes in FileDocumentProvider </ul> </li> <li>work with the Web Tools Platform project in order to improve overall integration with Platform Text and the platform in general</li> <li>Java editor <ul> <li>implement Search and Mark implementer occurrences</li> <li>revisit out-of-the-box colors and styles in the Java editor</li> <li>enable semantic syntax highlight per default</li> </ul> </li> <li>move Javadoc formatting to JDT Core</li> <li>start work on improved string externalization</li> <ul> <li>navigate from selected key in Java editor to definition in properties file editor</li> <li>show value when hovering over key in Java editor</li> <ul> <li>show value as is in the properties file</li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/glass.gif" nosave="" border="0" height="10" width="10"> show value as returned by the accessor class</li> </ul> <li>syntax coloring for Properties File Editor (comments, keys and values) <li>provide separate double-click strategy for key and value part in Properties File editor <li>navigate from selected key and value in properties file to location in Java editor and Plug-in Manifest editor <li>spell checking in Properties File editor and Externalize Strings wizard </ul> <li>cross team issues <ul> <li>contribute to the action contribution rework dynamic team</li> <li>contribute to the preferences rework dynamic team</li> </ul> </li> <li>PR triage </li> <ul> <li> PR that we definitively will not tackle for 3.1 will be resolved as LATER</li> <li>effectively communicate the guide lines the team uses to the community</li> </ul> </ul> <h5>Permanent items</h5> <ul> <li>bug fixing</li> <li>increase correctness test coverag</li> </ul> <h5>Proposed items</h5> <ul> <li>investigate lazy loading of document setup participants</li> </ul> <h4>Finished items/To be continued in M4</h4> <ul> <li>performance <ul> <li> continue performance tests <ul> <li>reflect about scope and applicability of test results (annotate test cases accordingly)</li> <li>complete performance tests for the published <a href="performance_scenarios.html">set of scenarios</a></li> </ul> </li> <li> improve performance <ul> <li>e.g., new line at end of commented StyledText.java</li> </ul> </li> </ul> </li> <li>continue with file buffer issues as outlined in the 3.1 plan <ul> <li>adapt existing code to document rewrite sessions <ul> <li>improve formatting performance</li> </ul> </li> <li>simplify temporal suspension of document partitioners for performance reasons <ul> <li>investigate lazy document partitioners</li> </ul> </li> </ul> </li> <li>continue with encoding issues listed in the 3.1 plan <ul> <li>integrate the 'Change Encoding...' action with the status editor shown in case of encoding errors</li> <li>re-establish encoding support for external files</li> <li>react to resource encoding changes in FileDocumentProvider </ul> </li> <li>work with the Web Tools Platform project in order to improve overall integration with Platform Text and the platform in general</li> <li>Java editor <ul> <li>implement Search and Mark implementer occurrences</li> <li>enable semantic syntax highlight per default</li> </ul> </li> <li>move Javadoc formatting to JDT Core</li> <li>start work on improved string externalization <ul> <li>navigate from selected key in Java editor to definition in properties file editor</li> <li>show value when hovering over key in Java editor <ul> <li>show value as is in the properties file</li> <li><img src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/images/glass.gif" nosave="" border="0" height="10" width="10"> show value as returned by the accessor class</li> </ul> </li> <li>syntax coloring for Properties File Editor (comments, keys and values) </li> <li>provide separate double-click strategy for key and value part in Properties File editor </li> </ul> </li> <li>cross team issues <ul> <li>contribute to the action contribution rework dynamic team</li> <li>contribute to the preferences rework dynamic team</li> </ul> </li> </ul> <h4>Items postponed to M4</h4> <ul> <li>PR triage </li> <ul> <li> PR that we definitively will not tackle for 3.1 will be resolved as LATER</li> <li>effectively communicate the guide lines the team uses to the community</li> </ul> <li>start work on improved string externalization</li> <ul> <li>navigate from selected key and value in properties file to location in Java editor and Plug-in Manifest editor <li>spell checking in Properties File editor and Externalize Strings wizard </ul> </ul> <h4>Testing</h4> <ul> <li> The <a href="testing/testpass_M3.html">test plan</a> for the M3 test pass.</li> </ul> <h3></h3> <hr> <h3>Milestone M2 </h3> <h4>Original Plan</h4> <h5>Commitments</h5> <ul> <li> finish 3.1 plan <ul> <li>work on resolving cross team issues</li> </ul> </li> <li>PR triage <ul> <li> PR that we definitively will not tackle for 3.1 will be resolved as Later</li> <li>effectively communicate PR team guide lines to the community</li> </ul> </li> <li>finish 3.0.1</li> <li> bug fixing <ul> <li>solve PRs that have been postponed between 3.0 RC1 - 3.0 GM</li> </ul> </li> <li> continue performance tests <ul> <li>grow number of available tests</li> <li>investigate into interactive tests</li> <li>collaborate with SWT to solve the issues with simulated user interaction</li> <li>reflect about scope and applicability of test results (annotate test cases accordingly)</li> <li>mature testing framework</li> </ul> </li> <li> improve performance <ul> <li>e.g., new line at end of commented StyledText.java</li> </ul> </li> <li> increase correctness test coverage</li> <li> provide J2SE 5 editor support</li> </ul> <h5>Proposed items</h5> <ul> <li>support @link in hovers</li> <li>start with file buffer issues as outlined in the overall plan</li> <li>start solving encoding issues listed in the plan</li> </ul> <h4>Finished items / To be continued into M3</h4> <h5></h5> <ul> <li>finish 3.1 plan</li> <li>finish 3.0.1</li> <li> bug fixing</li> <li> continue performance tests <ul> <li>grow number of available tests</li> <li>investigate into interactive tests</li> <li>collaborate with SWT to solve the issues with simulated user interaction</li> <li>mature testing framework</li> </ul> </li> <li> increase correctness test coverage</li> <li> provide J2SE 5 editor support</li> <li>start with file buffer issues as outlined in the overall plan</li> <li>start solving encoding issues listed in the plan</li> </ul> <h4>Added items</h4> <ul> <li>introduced "Open Untiled Text File"</li> <li>improve Smart Typing <ul> <li>stabilize linked mode</li> <li>improve auto indent strategies for code and Javadoc</li> </ul> </li> </ul> <h4>Items postponed to M3</h4> <ul> <li>PR triage <ul> <li> PR that we definitively will not tackle for 3.1 will be resolved as Later</li> <li>effectively communicate PR team guide lines to the community</li> </ul> </li> <li> continue performance tests <ul> <li>reflect about scope and applicability of test results (annotate test cases accordingly)</li> </ul> </li> <li> improve performance <ul> <li>e.g., new line at end of commented StyledText.java</li> </ul> </li> <li>support @link in hovers</li> </ul> <h4>Testing</h4> <ul> <li><a href="testing/testpass_M2.html">Test plan</a> for the M2 test pass.</li> </ul> <hr> <h3>Milestone M1</h3> <h4>Original plan</h4> <ul> <li>planning</li> <li>start working on performance tests <ul> <li>how to write performance test</li> <li>what is achievable with performance tests</li> <li>establish a performance test infrastructure</li> </ul> </li> <li>3.0.1 fixing</li> </ul> <h4>Finished items / To be continued into M2</h4> <h5></h5> <ul> <li>planning</li> <li>worked on performance tests <ul> <li>several performance test available</li> <li>establish a performance test infrastructure</li> </ul> </li> <li>3.0.1 fixing mostly done</li> </ul> <h4>Added items</h4> <ul> <li>support hyperlink navigation for URLs in comments</li> <li>introduce semantic highlighting for deprecated members</li> </ul> <h4>Testing</h4> <ul> <li><a href="testing/testpass_M1.html">Test plan</a> for the M1 test pass.</li> </ul> <p> </p> </td> </tr> <tr> <td></td> </tr> </table> <br> </body> </html>
| help@eclipse.org | ViewVC Help |
| Powered by ViewVC 1.0.3 |