Plan Item
From the 2.1 plan: "Provide user preferences. It should be possible to store user preferences that are not specific to a workspace separate from the workspace, so that they can be used in any workspace. [Platform Core, Platform UI] [Themes: User experience; Rich client platform]" (bug 36965)From the 3.0 plan: "The way that Eclipse deals with preferences should be improved. The workbench presentation of preferences generally uses a component-oriented hierarchy, which is not always the best choice for users. The UI should present preferences in such a way that users can readily discover them. Some preference settings have scopes (e.g., workspace-wide vs. per project). The UI should help the user to visualize these scopes. For team-wide uniformity, some preferences settings (e.g., compiler options) need to be shared (or imposed) across teams. The UI should also facilitate this. [Platform Core; Platform UI; Text; JDT UI; JDT Core]" (bug 71124)
Documents
- (obsolete) Reference: The original problem description.
- (obsolete) Reference: Proposed solution based on original description.
- Preferences API FAQ
- Plug-in Customization Story
- The Preferences Dynamic Team
- API Compatibility and Issues
- Issues on the Radar
Files
An example
plug-in which defines its own preference scope.
Related Bug Reports
- Bug 36965: [Preferences][Plan Item] Provide user settings
- Bug 42621: Preference Export mechanism needs to be changed
- Bug 43840: New read connection still using extssh
- Bug 47080: Accessing preferences from a Bundle
- Bug 47594: New preference exporting story
- Bug 50804: Preferences are inaccessible without loading the Plugin runtime class
- Bug 51309: [runtime] Preferences.setDefault should not store default-default values
- Bug 52515: JDT Debug does not honour plugin customization settings
- Bug 53456: Multiple Shared Project Settings
- Bug 71124: [plan item] Overhaul Preferences
- And a query for those who like to search...