Bug 214974 - [Workbench] Allow Workbench UI state to save/restore to user-provided Input/Output Streams
Summary: [Workbench] Allow Workbench UI state to save/restore to user-provided Input/O...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3.1   Edit
Hardware: PC Windows Vista
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-10 18:35 EST by G. Ralph Kuntz, MD CLA
Modified: 2014-02-03 10:09 EST (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description G. Ralph Kuntz, MD CLA 2008-01-10 18:35:40 EST 
Presently, all of the methods in Workbench that are involved in saving and restoring the workbench UI state are private.  This means that a developer of an application based on the RCP cannot override the location where the state is kept.

It would be very nice to be able to save and restore the UI state in a database so that clients could see the same screen layout even when using an application based on the RCP from different computers.
Comment 1 Tod Creasey CLA 2008-01-14 09:45:38 EST 
Something to consider if there is a workbench rework
Comment 2 Eric Moffatt CLA 2008-01-15 14:46:02 EST 
I'll mark this as 4.0 (where questions like this have a shot at clean answers).

Would something that allowed you to construct the 'root' IMemento work? This would likely be easier from our perspective...
Comment 3 G. Ralph Kuntz, MD CLA 2008-01-15 14:59:38 EST 
I'm not sure.  I haven't written an RCP application yet, but have done most of the tutorial in the Eclipse RCP book by McAffer, et al.

I suspect it would work if it let me save the IMemento after the workbench did and restore it before the workbench reads it from the file.

I was considering kludging it for now by doing this: grab the contents of the workbench.xml file from the filesystem after the save and before my application exits and over-writing it back to the filesystem the next time before calling "new WorkbenchAdvisor()".
Comment 4 Dani Megert CLA 2013-06-05 10:41:25 EDT 
Removing outdated target milestone.
Comment 5 Eric Moffatt CLA 2013-06-06 15:02:50 EDT 
This is part of implementing a way to have the UI Model (at least) separated from the Workspace it's being used to work on.

The main problem is to identify what we mean by 'ui state'. If it's just the UI Model then it's easy; if we want to include other state like preferences, dialog settings...then it's much more problematic (but still deserves a look).