Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 355825

Summary:

AbstractUIPlugin(loadDialogSettings()/getDialogSettings()/saveDialogSettings()) should be in user scope

Product:

[RT] RAP

Reporter:

Sebastien Arod <sebastien.arod>

Component:

Workbench

Assignee:

Project Inbox <rap-inbox>

Status:

ASSIGNED ---

QA Contact:

Severity:

enhancement

Priority:

CC:

digga1404, fr.appel

Version:

1.4

Target Milestone:

---

Hardware:

All

OS:

All

Whiteboard:

Attachments:

Description	Flags
Proposed patch based on preferences	none

Description Sebastien Arod

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

2011-08-31 05:41:07 EDT

Created attachment 202493 [details]
Proposed patch based on preferences

Comment 2 Arnaud MERGEY

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

2013-07-22 03:25:39 EDT

*** Bug 241648 has been marked as a duplicate of this bug. ***