Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355825 - AbstractUIPlugin(loadDialogSettings()/getDialogSettings()/saveDialogSettings()) should be in user scope
Summary: AbstractUIPlugin(loadDialogSettings()/getDialogSettings()/saveDialogSettings(...
Status: ASSIGNED
Alias: None
Product: RAP
Classification: RT
Component: Workbench (show other bugs)
Version: 1.4   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 241648 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-08-25 08:38 EDT by Sebastien Arod CLA
Modified: 2013-07-22 03:25 EDT (History)
2 users (show)

See Also:

Attachments
Proposed patch based on preferences (4.70 KB, patch)
2011-08-31 05:41 EDT, Arnaud MERGEY CLA 		no flags Details | Diff
View All 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 Sebastien Arod CLA 2011-08-25 08:38:47 EDT 
Build Identifier: 

The implementation of AbstractUIPlugin(loadDialogSettings()/getDialogSettings()/saveDialogSettings()) is still the RCP implementation which is application scoped and store the settings in  the dialog_settings.xml file.

Those settings should be user specific. Ideally the way to store those (file or other) should be customizable similarly to what is done for Preferences Storage.


Reproducible: Always
Comment 1 Arnaud MERGEY CLA 2011-08-31 05:41:07 EDT 
Created attachment 202493 [details]
Proposed patch based on preferences
Comment 2 Arnaud MERGEY CLA 2011-08-31 05:48:23 EDT 
A patch proposal to solve this issue based on eclipse preferences, the dialog content is read/write in a org.eclipse.rap.ui.workbench preference, instead of the common files.

It allows to have one settings per users and relies on preferences customization mechanism (through RWT ISettingStore).
Comment 3 Ivan Furnadjiev CLA 2013-07-22 03:25:39 EDT 
*** Bug 241648 has been marked as a duplicate of this bug. ***