*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|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.

*Intro: We have to provide a 4.2 specific implementation for the IntroManager. We should be able to do this in a more organized fashion than currently exists in 3.x

*Intro: We have to provide a 4.2 specific implementation for the IntroManager. We should be able to do this in a more organized fashion than currently exists in 3.x

*Splash: We need to update the splash screen so that it is at least equivalent to the 3.x version. Note thtat this will depend on out getting the startup logic fixed at least to the point of not 'finishing' until the UI is actually displayed.

*Splash: We need to update the splash screen so that it is at least equivalent to the 3.x version. Note thtat this will depend on out getting the startup logic fixed at least to the point of not 'finishing' until the UI is actually displayed.

Revision as of 14:55, 6 July 2011

This page is under construction.

For now we'll use this to capture the list of work items that we intend to address during the 4.2 development cycle.

Work Items

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.

Intro: We have to provide a 4.2 specific implementation for the IntroManager. We should be able to do this in a more organized fashion than currently exists in 3.x

Splash: We need to update the splash screen so that it is at least equivalent to the 3.x version. Note thtat this will depend on out getting the startup logic fixed at least to the point of not 'finishing' until the UI is actually displayed.

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

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...

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.