* [[Image:Progress.gif]] (Kim) {{Bug|246875}}. '''Extensible About Experience''' it would significantly improve the user experience if there was a way to tie the bundles presented in the About dialog to the mechanism that's capable of updating the bundles. However, hardcoding knowledge of the update manager is unacceptable. If the About experience was plugable, however, we might be able to achieve such a unified experience without harming the traditional RCP users who may not desire it. See {{bug|246875}} for details. (proposed)

* [[Image:Progress.gif]] (Kim) {{Bug|246875}}. '''Extensible About Experience''' it would significantly improve the user experience if there was a way to tie the bundles presented in the About dialog to the mechanism that's capable of updating the bundles. However, hardcoding knowledge of the update manager is unacceptable. If the About experience was plugable, however, we might be able to achieve such a unified experience without harming the traditional RCP users who may not desire it. See {{bug|246875}} for details. (proposed)

* [[Image:Glass.gif]] (Kim) '''Unified Desktop Notification Support''' Both Mylyn and Jazz implement their own mechanism for displaying desktop notifications (popups). A unified API that they can both share should exist at the workbench level. Please see {{bug|209911}} and {{bug|177974}} for details. (proposed)

* [[Image:Glass.gif]] (Kim) '''Unified Desktop Notification Support''' Both Mylyn and Jazz implement their own mechanism for displaying desktop notifications (popups). A unified API that they can both share should exist at the workbench level. Please see {{bug|209911}} and {{bug|177974}} for details. (proposed)

(Markus Kuppe, Versant) Multi-instance Properties View - bug 248103 The properties view does not allow a user to look at the properties of multiple items at the same time. We would like the ability to pin a properties view to one object and be able to open a different properties view for a different object, so they can be compared. (proposed)

(Matthew Bisson, Eric) Improved Customization Support - The current "Customize Perspective" dialog is not very usable. Ideally, users should be able to hide UI elements (menu, toolbar, wizards, context menu, ...) that they don't need, and bring back previously hidden UI elements. Changing the order of UI elements may be too difficult given our current architecture. (proposed - see bug 182714)

(Eric, Paul) WPF Roll with any requirements, if any, springing from the SWT WPF port. (proposed)

(Kim) bug 246875. Extensible About Experience it would significantly improve the user experience if there was a way to tie the bundles presented in the About dialog to the mechanism that's capable of updating the bundles. However, hardcoding knowledge of the update manager is unacceptable. If the About experience was plugable, however, we might be able to achieve such a unified experience without harming the traditional RCP users who may not desire it. See bug 246875 for details. (proposed)

(Kim) Unified Desktop Notification Support Both Mylyn and Jazz implement their own mechanism for displaying desktop notifications (popups). A unified API that they can both share should exist at the workbench level. Please see bug 209911 and bug 177974 for details. (proposed)

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

Milestone M7 (2009-05-01) (Performance, Polish)

Working on our test suites day: March 16, 2008

Working on performance day: March 17, 2008

Ideas

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)

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?)