Milestone RC4 Plan

Top items

• testing (test pass four test plan)
• documentation (3.1 documentation plan)
• stop ship bug fixing

Milestone RC3 Plan

Top items

• testing (test pass three test plan)
• [3.1 RC4] documentation (3.1 documentation plan)
• critical bug fixing

Milestone RC2 Plan

Top items

• testing (test plan test pass two test plan)
• bug fixing

Milestone RC1 Plan

Top items

• polish
• bug fixing

Testing

• The test plan for the test pass one.

Milestone M7 Plan

Top items

• performance
• adopt changes/features from other components
• polish

Committed items

• Cross-team issues

  • find a solution for editor splitting
  • remove "Open Untitled Text File" from File menu (bug 76816)

• J2SE 5.0 support (JDT UI's overall status)

  • improve accurracy of auto-boxing

• Adopt changes/features from other components

  • Help view: allow to contribute top-level section (depends on Platform Help bug 85721). If fixed, promote "Java help:" to top-level section
  • adopt new content-type editor lookup (bug 37668)
  • adapt new SelectionEvent#text field where we use the Link widget (bug 86608)
  • remove deprecation form plugin.xml files i.e. switch to use org.eclipse.ui.bindings extension point
  • use virtual table for code assist popup
  • [3.1 RC3] provide component.xml for text plug-ins
  • provide test coverage information for text plug-ins
  • migrate to new bundle story i.e. provide MANIFEST.MF
  • convert plug-ins to JARed format
  • [3.1 RC1] adopt "showURL" API for URL hyperlink (bug 69647)
  • adopt mixed indent support (bug 73104)

• Polish

  • preference pages:
  • remove collapsible sections
  • [3.1 RC1] add and test mnemonics on all pages
  • track Platform UI bug 88031: Allow to show all preferences
  • [>3.1] (improve syntax color preference page: click in preview should select items in list)
  • improve folding icon (bug 61725)
  • synchronize editor dirty bit with undo state (bug 21493)
    Note: A modification stamp needs to be added to the document and the document event (API changes)
  • [3.1 RC1] add support for default line delimiter (bug 3970) - work might continue in RC1
  • [3.1 RC1] polish content assist (items TBD)

• (Code cleanup)

  • [>3.1] find dead code
  • [>3.1] reference to AnnotationExpandHover in JavaExpandHover
  • [>3.1] references to Search plug-in in PropertyKeyHyperlink see: bug 87751

Permanent items

• bugzilla inbox tracking
• bug fixing
• increase correctness test coverage

Proposed items

• [>3.1] add UI for Word Completion similar to code assist
• [>3.1] add new org.eclipse.ltk.ui plug-in to release
  Note: This item depends on the above mentioned cross team-issue

• [>3.1] (RCP)

  • add support for annotation presentation and navigation
  • investigate declaring org.eclipse.resources optional for org.eclipse.core.filebuffers
  • provide an example RCP text editor application with the following features:
    
    • open an external file
    • open an untitled (new & empty) text file
    • save
    • spell checking
    • quick fix to fix spelling problems

Absences

• Dani: 2 days vacation
• Tom: 5½ days vacation
• 2½ public holidays

Testing

• The test plan for the M7 test pass.

Milestone M6 Plan

Top five items

• continue with J2SE 5.0 support (JDT UI's overall status)
• [>3.1] progress in consolidating the platform
• provide NLS tooling for new Platform Core's new message bundle approach
• finalize existing 3.1 APIs (M6 is API freeze)
• performance

Committed items

• () Cross-team issues

  • resolve missing performance test fingerprints problem
  • adopt global operation history
  • help push down formatter to JDT Core
  • apply mixed indent patch for fomatter together with JDT Core
  • [>3.1] (provide a compatibility layer for commands moved to LTK UI plug-in)
    a hard-coded patch is ready but there should be support from the Platform for extension-point evolution.

• () J2SE 5.0 support (JDT UI's overall status)

  • () fix bugs introduced in M5
    • performance impact due to parameter guessing
    • [3.1 M7] improve accurracy of auto-boxing
    • problems introduced by new projection caption support
  • improve content assist for generics (work together with David Audel / JDT Core):
    • better type parameter proposals
    • better enum constant proposals
  • [>3.1] (provide new semantic highlightings)
  • type bounds
  • enums
  • static imports

• [>3.1] Platform consolidation

  • push down annotation navigation
  • push down annotation hovers
  • adopt and push down Quick Assist and Quick Fix infrastructure
  • offer spelling checking in Text editor
  • (move Occurrences annotation type definition and annotation specification down to ltk.ui or editors.ui)
  • (push down annotation navigation)

• NLS tooling

  • provide tooling for Platform Core's new message bundle approach
  • provide new back-end for the NLS wizard that can write the new format
  • [>3.1] (improve Properties File editor)
  • (ensure correct ISO-8859-1 encoding when writing a properties file)
  • [>3.1] (improve Externalize Strings wizard)
    • (spell checking)
    • (ensure correct ISO-8859-1 encoding when writing a properties file)

• [3.1 M7] (Code cleanup)

  • reference to AnnotationExpandHover in JavaExpandHover
  • references to Search plug-in in PropertyKeyHyperlink

• R3.0.2 related work items

  • testing
  • bug verification
  • ship 3.0.2

• participate in writing an article for the JavaMagazin

Permanent items

• bugzilla inbox tracking
• bug fixing
• increase correctness test coverage

Proposed items

• [>3.1] add UI for Word Completion similar to code assist
• [>3.1] add new org.eclipse.ltk.ui plug-in to release
  Note: This item depends on the above mentioned cross team-issue

• [>3.1] (RCP)

  • add support for annotation presentation and navigation
  • investigate declaring org.eclipse.resources optional for org.eclipse.core.filebuffers
  • provide an example RCP text editor application with the following features:
    
    • open an external file
    • open an untitled (new & empty) text file
    • save
    • spell checking
    • quick fix to fix spelling problems

Absences

• Dani: 5 days vacation
• Tom: 5 days eclipseCon
• Tom: 5 days vacation
• 2 public holidays

Testing

• The test plan for the M6 test pass.

Milestone M5

Top five items

• start with J2SE 5.0 support (JDT UI's overall status)
• progress in consolidating the platform
• progress in improving NLS tooling
• remove dependencies to internal code from other plug-ins
• R3.0.2 related work items

Committed items

• Cross-team issues

  • resolve performance test problems
  • participate in the action contribution dynamic team
  • harmonize with potential global undo manager
    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.
  • provide feedback for new Component Framework proposal (⇒ editor splitting)
  • finish pushing down formatter to JDT Core
  • provide a compatibility layer for commands moved to LTK UI plug-in:
    a hard-coded patch is ready but there should be support from the Platform for extension-point evolution.

• J2SE 5.0 support (JDT UI's overall status)

  • investigate impact on the following JDT Text areas:
    • syntax highlighting
    • content assist
    • hovering
    • comment formatting
    • typing
    • Java Outline page
    • folding
    • mark occurrences
  • start to fix problems encountered in above investigation
  • provide new templates
  • provide new semantic highlightings
  • autoboxing
  • type bounds
  • enums
  • static imports

• Platform consolidation

  • start adopting and pushing down Quick Assist and Quick Fix infrastructure
  • push down annotation hovers
  • offer spelling checking in Text editor
  • (move Occurrences annotation type definition and annotation specification down to ltk.ui or editors.ui)
  • (push down annotation navigation)

• () NLS tooling

  • fix bugs reported in M4 test pass
  • () improve Properties File editor
    • improve detection of NLS accessor's resource bundle
    • reduce false positives when navigating from Properties file editor to key references
    • (ensure correct ISO-8859-1 encoding when writing a properties file)
  • (improve Externalize Strings wizard)
    • (spell checking)
    • (ensure correct ISO-8859-1 encoding when writing a properties file)
  • investigate impact of Platform Core's new message bundle approach

• Code cleanup

  • identify dependencies to other plug-ins and request API if appropriate
    The following API requests have been filed:
    • 79419 [Preferences] Need a link component
    • 82256 [Contributions] Need EditorPluginAction and ActionDescriptor.ATT_DEFINITION_ID as API
      This will not be provided as there will be a new command story. We will keep the internal references until this is available.
  • remove dependencies to internal code from other plug-ins
  Most of them got fixed in M5. Besides the one mentioned above remaion for M6:
  • reference to AnnotationExpandHover in JavaExpandHover
  • references to Search plug-in in PropertyKeyHyperlink

• R3.0.2 related work items

  Fixed two bugs.

Permanent items

• bugzilla inbox tracking
• bug fixing
• increase correctness test coverage

Proposed items

• add new org.eclipse.ltk.ui plug-in to release
  Note: This item depends on the above mentioned cross team-issue
• (Provide an example RCP text editor application with the following features:)
  
  • open an external file
  • open an untitled (new & empty) text file
  • save
  • spell checking
  • quick fix to fix spelling problems
  Note: it will require org.eclipse.core.resources plug-in

Absences

• Tom: 3 days vacation

Testing

• The test plan for the M5 test pass.

Milestone M4

Original Plan

Top Five

• complete performance tests
• rework preferences
• finish file buffer operations
• progress in consolidating the platform
• improve NLS tooling

Committed items

Cross-team issues

• consolidate Ant, Platform UI, WTP, VE feedback and issues
• editor embedding and splitting
  • provide prototype for services architecture
  • investigate how splitting would look like in a "component" world
• participate in preferences dynamic team
• participate in the action contribution dynamic team
• work on and adapt to the new undo story
• migrate to the changed semantics of IPath
• finish pushing down formatter to JDT Core

Testing

• complete performance tests for the published set of scenarios

Component work

• rework preferences
  • find all sharing scenarios (appearance, behavior, hovering, etc. ....)
  • functional categorization
  • check how WTP and other larger clients fit in
  • implement different scenarios
  • initiate review by usability team
• finish file buffer operations
  • solve memory issues
  • improve test coverage
  • integrate with ltk core change architecture
  • solve typing raise conditions
• add document partitioning to StorageDocumentProvider
  • [investigate] exploit the existing filebuffer extension points
• Java editor
  • initial color settings
  • enable semantic highlighting by default
• Default text editor
  • everything we push down while consolidating the platform needs to have a surfacing new function in the default text editor
  • pushing down spell checking allows us to check whether the push down of the quick fix infrastructure is successful
    

Platform consolidation

• create plug-in for 'Editing Source Scope'
  • move Occurrences annotation type definition and annotation specification down to ltk.ui or editors.ui
• push down Ctrl-Click
  • [investigate] general resolution infrastructure
• push down annotation navigation
• push down spell checking
• start adopting and pushing down Quick Fix infrastructure
  

Code cleanup

• fix IEditorHelper
  • use names that are self-describing and don't hamper further development
• finish work on new functions not yet API
  

NLS tooling

• improve Properties File editor
  • fix reported syntax coloring issues
  • navigate from selected key and value in a properties file to the location of usage in Java editor and Plug-in Manifest editor
  • spell checking
  • ensure correct ISO-8859-1 encoding when writing a properties file
• support new nls features in Class file editor
  • coloring
  • hovering
  • navigation
• improve Externalize Strings wizard
  • spell checking
  • ensure correct ISO-8859-1 encoding when writing a properties file
• investigate whether we can improve NLS tooling to support the string externalization approach used in TextOperationAction

Permanent items

• bug fixing
• increase correctness test coverage

Proposed items

• implement a SaveAs dialog that allows to save inside and outside of the workspace
  • involved parties: Platform UI, SWT, send patch to Platform UI
• lazy loading of document setup participants
• allow for extending file buffers with custom implementations
• allow templates in the default text editor
• generalize and push down InformationDispatchAction
• generalize push down quick view support
  • Outline presentation control, AbstractInformationControl and related
• [investigate] Consolidate SourceViewerInformationControl and all of its copies
• [investigate] allow for an outline mode in the default text editor
  • folding just based on indentation
  • opens the way for using QuickOutline in the default text editor
  
  

Finished

Cross-team issues

• consolidate Ant, Platform UI, WTP, VE feedback and issues
• editor embedding and splitting
  • provide prototype for services architecture
  • investigate how splitting would look like in a "component" world
• participate in preferences dynamic team
• migrate to the changed semantics of IPath

Testing

• complete performance tests for the published set of scenarios

Component work

• rework preferences
  • find all sharing scenarios (appearance, behavior, hovering, etc. ....)
  • functional categorization
  • check how WTP and other larger clients fit in
  • implement different scenarios
  • initiate review by usability team
• finish file buffer operations
  • improve test coverage
• Java editor
  • enable semantic highlighting by default

Platform consolidation

• create plug-in for 'Editing Source Scope'
• push down Ctrl-Click
  • [investigate] general resolution infrastructure

Code cleanup

• fix IEditorHelper
  • use names that are self-describing and don't hamper further development
• finish work on new functions not yet API
  

NLS tooling

• improve Properties File editor
  • fix reported syntax coloring issues
  • navigate from selected key and value in a properties file to the location of usage in Java editor and Plug-in Manifest editor
  • spell checking
• support new nls features in Class file editor
  • coloring
  • hovering
  • navigation

Not Finished / Deferred to M5

Cross-team issues

• participate in the action contribution dynamic team
• finish pushing down formatter to JDT Core
• work on and adapt to the new undo story

Platform consolidation

• (move Occurrences annotation type definition and annotation specification down to ltk.ui or editors.ui)
• (push down annotation navigation)
• push down spell checking
• start adopting and pushing down Quick Fix infrastructure
  

NLS tooling

• improve Properties File editor
  • ensure correct ISO-8859-1 encoding when writing a properties file
• improve Externalize Strings wizard
  • spell checking
  • ensure correct ISO-8859-1 encoding when writing a properties file

Deferred For Now

Component work

• finish file buffer operations
  • solve memory issues
  • integrate with ltk core change architecture
  • solve typing raise conditions
• add document partitioning to StorageDocumentProvider
  • [investigate] exploit the existing filebuffer extension points
• Java editor
  • initial color settings

NLS tooling

• investigate whether we can improve NLS tooling to support the string externalization approach used in TextOperationAction

Proposed items

• implement a SaveAs dialog that allows to save inside and outside of the workspace
  • involved parties: Platform UI, SWT, send patch to Platform UI
• lazy loading of document setup participants
• allow for extending file buffers with custom implementations
• allow templates in the default text editor
• generalize and push down InformationDispatchAction
• generalize push down quick view support
  • Outline presentation control, AbstractInformationControl and related
• [investigate] Consolidate SourceViewerInformationControl and all of its copies
• [investigate] allow for an outline mode in the default text editor
  • folding just based on indentation
  • opens the way for using QuickOutline in the default text editor
  
  

Testing

• The test plan for the M4 test pass.

Milestone M3

Original Plan

Committed items

• performance
  • continue performance tests
    • reflect about scope and applicability of test results (annotate test cases accordingly)
    • complete performance tests for the published set of scenarios
  • improve performance
    • e.g., new line at end of commented StyledText.java
• continue with file buffer issues as outlined in the 3.1 plan
  • adapt existing code to document rewrite sessions
    • improve formatting performance
  • simplify temporal suspension of document partitioners for performance reasons
    • investigate lazy document partitioners
• continue with encoding issues listed in the 3.1 plan
  • integrate the 'Change Encoding...' action with the status editor shown in case of encoding errors
  • re-establish encoding support for external files
  • react to resource encoding changes in FileDocumentProvider
• work with the Web Tools Platform project in order to improve overall integration with Platform Text and the platform in general
• Java editor
  • implement Search and Mark implementer occurrences
  • revisit out-of-the-box colors and styles in the Java editor
  • enable semantic syntax highlight per default
• move Javadoc formatting to JDT Core
• start work on improved string externalization
• navigate from selected key in Java editor to definition in properties file editor
• show value when hovering over key in Java editor
• show value as is in the properties file
• show value as returned by the accessor class
• syntax coloring for Properties File Editor (comments, keys and values)
• provide separate double-click strategy for key and value part in Properties File editor
• navigate from selected key and value in properties file to location in Java editor and Plug-in Manifest editor
• spell checking in Properties File editor and Externalize Strings wizard
• cross team issues
  • contribute to the action contribution rework dynamic team
  • contribute to the preferences rework dynamic team
• PR triage
• PR that we definitively will not tackle for 3.1 will be resolved as LATER
• effectively communicate the guide lines the team uses to the community

Permanent items

• bug fixing
• increase correctness test coverag

Proposed items

• investigate lazy loading of document setup participants

Finished items/To be continued in M4

• performance
  • continue performance tests
    • reflect about scope and applicability of test results (annotate test cases accordingly)
    • complete performance tests for the published set of scenarios
  • improve performance
    • e.g., new line at end of commented StyledText.java
• continue with file buffer issues as outlined in the 3.1 plan
  • adapt existing code to document rewrite sessions
    • improve formatting performance
  • simplify temporal suspension of document partitioners for performance reasons
    • investigate lazy document partitioners
• continue with encoding issues listed in the 3.1 plan
  • integrate the 'Change Encoding...' action with the status editor shown in case of encoding errors
  • re-establish encoding support for external files
  • react to resource encoding changes in FileDocumentProvider
• work with the Web Tools Platform project in order to improve overall integration with Platform Text and the platform in general
• Java editor
  • implement Search and Mark implementer occurrences
  • enable semantic syntax highlight per default
• move Javadoc formatting to JDT Core
• start work on improved string externalization
  • navigate from selected key in Java editor to definition in properties file editor
  • show value when hovering over key in Java editor
    • show value as is in the properties file
    • show value as returned by the accessor class
  • syntax coloring for Properties File Editor (comments, keys and values)
  • provide separate double-click strategy for key and value part in Properties File editor
• cross team issues
  • contribute to the action contribution rework dynamic team
  • contribute to the preferences rework dynamic team

Items postponed to M4

• PR triage
• PR that we definitively will not tackle for 3.1 will be resolved as LATER
• effectively communicate the guide lines the team uses to the community
• start work on improved string externalization
• navigate from selected key and value in properties file to location in Java editor and Plug-in Manifest editor
• spell checking in Properties File editor and Externalize Strings wizard

Testing

• The test plan for the M3 test pass.

Milestone M2

Original Plan

Commitments

• finish 3.1 plan
  • work on resolving cross team issues
• PR triage
  • PR that we definitively will not tackle for 3.1 will be resolved as Later
  • effectively communicate PR team guide lines to the community
• finish 3.0.1
• bug fixing
  • solve PRs that have been postponed between 3.0 RC1 - 3.0 GM
• continue performance tests
  • grow number of available tests
  • investigate into interactive tests
  • collaborate with SWT to solve the issues with simulated user interaction
  • reflect about scope and applicability of test results (annotate test cases accordingly)
  • mature testing framework
• improve performance
  • e.g., new line at end of commented StyledText.java
• increase correctness test coverage
• provide J2SE 5 editor support

Proposed items

• support @link in hovers
• start with file buffer issues as outlined in the overall plan
• start solving encoding issues listed in the plan

Finished items / To be continued into M3

• finish 3.1 plan
• finish 3.0.1
• bug fixing
• continue performance tests
  • grow number of available tests
  • investigate into interactive tests
  • collaborate with SWT to solve the issues with simulated user interaction
  • mature testing framework
• increase correctness test coverage
• provide J2SE 5 editor support
• start with file buffer issues as outlined in the overall plan
• start solving encoding issues listed in the plan

Added items

• introduced "Open Untiled Text File"
• improve Smart Typing
  • stabilize linked mode
  • improve auto indent strategies for code and Javadoc

Items postponed to M3

• PR triage
  • PR that we definitively will not tackle for 3.1 will be resolved as Later
  • effectively communicate PR team guide lines to the community
• continue performance tests
  • reflect about scope and applicability of test results (annotate test cases accordingly)
• improve performance
  • e.g., new line at end of commented StyledText.java
• support @link in hovers

Testing

• Test plan for the M2 test pass.

Milestone M1

Original plan

• planning
• start working on performance tests
  • how to write performance test
  • what is achievable with performance tests
  • establish a performance test infrastructure
• 3.0.1 fixing

Finished items / To be continued into M2

• planning
• worked on performance tests
  • several performance test available
  • establish a performance test infrastructure
• 3.0.1 fixing mostly done

Added items

• support hyperlink navigation for URLs in comments
• introduce semantic highlighting for deprecated members

Testing

• Test plan for the M1 test pass.