[platform-ui-dev] Migration issues for UI persistence

[Randy Hudson <hudsonr@xxxxxxxxxx>]

When shutting down, the workbench persists
which views are open and where.  When moving from release 2.X to 3.0,
it may be possible that Views had their IDs renamed.  For example,
a view that was provided by Tool X, was pushed up into framework G.  It
is possible to update references in perspectives which used this view,
but it isn't possible to update the persisted window state.

To solve this problem, could Tool X
provide a migration mapping in their plugin.xml?  Stating that View
xyz is now replaced by view abc?  Otherwise, I think you get a popup
dialog stating that a view could not be restored when restarting a workspace
the first time.

-Randy