Skip to main content
Jump to: navigation, search

Platform UI/Plan/3.6


  • Stability
  • Contributions from the Community
  • BiDi
  • Accessibility
  • e4 (Note that e4 work does not appear on this plan.)


The following sections contain proposed and committed items that (as of September 2009) we think will be worked on during the 3.6 development cycle. For completed work, have a look at our build notes. If you would like to help out, please see Platform_UI/How_to_Contribute.

Milestone M1 (2009-08-07)

  • e4 work

Milestone M2 (2008-09-18)

  • e4 work

Milestone M3 (2008-10-30)

  • e4 work
  • (Equinox work - Progress.gif (Oleg) bug 244468 Support reading extension registry in any locale.)
  • Progress.gif (Szymon, Serge, John) bug 288556 Backporting the e4 Flexible Resources work into 3.6.
  • Glass.gif Focus on accessibility (Prakash, Hitesh) bug 252646

Milestone M4 (2008-12-11)

  • e4 work
  • Glass.gif (Boris, Susan) bug 288550 Windows 7 (Win32) fragment, potential contributions: native search field, application menu, colors, ...
  • Glass.gif Focus on accessibility (Prakash, Hitesh) bug 252646
  • Glass.gif BiDi improvements (Oleg, Dina, Mohamed, Semion) bug 288554

Milestone M5 (2009-01-29) (Major Features Done)

  • e4 work
  • Glass.gif Focus on accessibility (Prakash, Hitesh) bug 252646
  • Glass.gif BiDi improvements (Oleg, Dina, Mohamed, Semion) bug 288554
  • Glass.gif Focus on compatibility (all) bug 288559

Milestone M6 (2009-03-12) (API Freeze)

  • e4 work
  • Glass.gif Focus on accessibility (Prakash, Hitesh) bug 252646
  • Glass.gif BiDi improvements (Oleg, Dina, Mohamed, Semion) bug 288554
  • Glass.gif Focus on compatibility (all) bug 288559

Milestone M7 (2009-04-30) (Feature Freeze, Performance, Polish)


The remainder of this page contains blue sky thinking about the kind of things we would like to see in the immediate future of the Platform UI component. This is a place to collect ideas - it does not represent a commitment to implement the ideas.

Note that items marked as "proposed" are just that - we don't know yet how much time we'll have or how many of the items we will be able to work on for 3.5. If you are not currently a committer but would like to work on any of these items, please don't hesitate to contact us - you can also refer to the contribution guide.

Ongoing efforts

We usually spend time on all of the following.

  • Working with the community, especially when there are patches or code contributions
  • Testing (both manual testing, and improving the test suites)
  • Regressions
  • Bug fixing
  • Performance
  • UI consistency
  • Exposing existing functionality as API where necessary (e.g. when important functionality required access to internals)
  • Accessibility
  • Internationalization, BiDi
  • Polish
  • Reliability / Stability / Security
  • Currency (new platforms, new versions of SWT, ICU4J, ...)

Common Navigator

  • Clear backlog of bugs, certainly all major and higher
  • Add support for Commands
  • Come up to par with the Package Explorer (detailed list of items to be provided)

Data Binding

  • Builder API. Add API for easier building of bindings and their update strategies. (proposed - see bug 203492)
  • Integrating Community contributions. We have a number of patches that were submitted - these need to be reviewed and released. (committed)

Commands and Contributions

  • Global Actions - requests
    • Requests for new commands/actions: ex: CollapseAll, ExpandAll, Clean Project, etc
  • Framework Cleanup - Further conversions of action framework to command framework
  • Command Framework - unimplemented aspects of the command framework
    • Better support for toggle buttons and radio buttons, persistence of their state, etc
    • More enhancements to the KeyBinding page
    • Dynamic service support
    • Service/SourceProvider re-evaluation. Our Source Providers need to be consistent and we should be providing useful property testers as API
    • Providing appropriate context to handlers updating UI elements, for example
    • provide the menu override framework - allow specific menu items/toolbar items to be customized (feature-level work)
    • Examine the global application context
    • perhaps provide image extension attributes can access shared images
    • how should menu contributions and potentially keybindings be provided/restricted to a product or application
  • Macro Recording I'd like to investigate if we can provide a simple macro recording mode, some form of key events + parameterized commands, that could then be played back (related to bug 80140?)

Tabbed Properties

  • Tabbed Properties Improvements Incremental improvements to the tabbed properties support, such as the ability to get/set the currently active tab/section in the view. (proposed)

Misc (we should split this into themes when appropriate)

  • Review of Cross-Boundry API Usage Review use of non-API in client code and investigate promotion of code to API where appropriate. (proposed)
  • Sharable Working Sets. The usefulness of working sets is limited by the fact they are not team sharable. An option to tag resources with the information, or the ability to generate a project with the working set info could be implemented. (proposed)
  • Editor Support Look at support for per-perspective editors (bug 11001) and full-screen editing mode. Also review some possible enhancements to MultiPageEditorPart (fire change events when page changes per bug 201391? MPEP as a metaphor for 1st class editor navigation?)


Glass.gif Needs some investigation

Progress.gif Patch in progress

Ok green.gif Bug fixed / Feature added

Back to the top