Bug 80024 - [RCP] [Preferences] Allow WorkbenchAdvisor control over location of persisted settings
Summary: [RCP] [Preferences] Allow WorkbenchAdvisor control over location of persiste...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-02 10:50 EST by Jean-Michel Lemieux CLA
Modified: 2019-09-06 16:14 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jean-Michel Lemieux CLA 2004-12-02 10:50:20 EST
3.0
Currently the workbench saves the following settings in the instance area:
- editor registry
- perspective registry
- working sets
- dialog settings

It would be nice if an application could decide where these settings are put. If
a configuration area doesn't exist, then it could use a user area, application
scoped configuration area (e.g. can't assume that config area is shared by all
RCP applications). Current running with @none or @noDefault doesn't support the
workbench saving it's settings (e.g. perspectives are always reset).

I think this fits in with the preference story, and we should investigate if it
can make 3.1?
Comment 1 Nick Edgar CLA 2006-03-15 11:24:23 EST
Reassigning bugs in component areas that are changing ownership.
Comment 2 Boris Bokowski CLA 2009-11-26 16:16:30 EST
Prakash is now responsible for watching bugs in the [RCP] component area.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:14:05 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.