3.1 Development Effort - Previous Milestone Plans

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
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
  • participate in preferences dynamic team
  • migrate to the changed semantics of IPath
Testing
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
  • 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
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
  • 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

Testing

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

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

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