Eclipse 4 RCP Improvements

bug 351363 RCP Views: We have to refactor some of the more common views to be usable in 4.x RCP apps without dragging in the compatibility payer. This will mean changes in both the 3.x and 4.x streams since it will mean turning these views into 'real' 4.x parts and then hosting them in 3.x through the use of Tom's 'forward compatibility' layer.

bug 350251 Refactor and extract bits from the org.eclipse.ui.workbench and org.eclipse.ui.forms bundles so that they can be reused in 4.x RCP applications

Updating AddOns and Fragment processing

bug 341732 - AddOns should have an "order" property that allows sorting to determine run order

bug 324954 - [Model] Allow model fragments to use XPath-Syntax to decide where to contribute

Consuming new Eclipse 4 Features

These are the tasks needed to allow both existing and new Eclipse plug-ins to gain access to Eclipse 4's underlying API and use these to enhance their own component's User Interface.

bug 351366 Hosted Views / Editors: We have to allow views and editors to be hosted in Dialogs, Wizards etc. At the moment it appears that there are a number of places (i.e. selection) where a part that isn't the active part doesn't work (and you also can't make a part that isn't part of the presentation structure active).

Dependency Injection and Architecture

Service lookup simplification using eclipseContext.getActiveLeaf()

bug 341416 - Selection consumption for handlers using a single variable

bug 320932 - [Compatibility] Can't start Eclipse 4 SDK with proxy authentication. Note that this will depend on out getting the startup logic fixed at least to the point of not 'finishing' until the UI is actually displayed.

bug 349867 DnD Polish: We've got to be able to do something better than the feedback we currently have. Also need to implement DnD for trim elements...

bug 348599 Can't create stacks of another orientation after one already exists in the shared area

bug 351367 Investigate eliminating the use of 'deltas': We need to see if there's an alternative implementation in which the model is stored using the EMF mechanisms. By preference we'd prefer to include the Menu/TB info in the saved model and handle missing bundles etc during rendering / run time rather than trying to clear the elements out of the model before saving.