| Re: [e4-dev] Unique Id generation Proposal |
On Fri, Mar 12, 2010 at 8:49 AM, Sven Efftinge <sven.efftinge@xxxxxxxxx> wrote:
> Is the programmatically modified model persisted between sessions?
Yes and no. The deltas between the starting model and the modified model at shutdown are persisted (via ChangeRecorder) but the modified model itself is not persisted. This is in place for supporting merging.
In 3.x, we have the following scenario...
1. Consider an RCP application with a window and a part stack with two parts and a third part that's not shown by default.
2 .The user shows this third part.
3. The entire workbench state is persisted.
4. The user upgrades to a new version of the RCP application which now has a new part in the stack by default. However, since the persisted state only has the three original parts, the new part will not be displayed in the stack and the "automatic discovery" of the new feature is gone because the user is forced to open the view manually. People that have used perspectiveExtensions for wizard shortcuts (like yours truly) have likely fallen to bug 48060.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=48060
In e4, by recording the deltas, we merely record the fact that part C was added to the stack in step 3.
Originally, we have A, B and the user has modified the stack to be A, B, C. Now the new version's stack has A, B, D, we apply a primitive 3-way merge which (should ;)) decide to show all four parts to the user when the new version of the application has started up.
Regards,
Remy
----------
Remy Suen
Eclipse Platform/UI Committer
IBM Ottawa
613-356-5162