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

Bug 85723

Summary: [Preferences] Organize preferences by concepts instead of implementation
Product: [Eclipse Project] Platform Reporter: Randy Hudson <hudsonr>
Component: UIAssignee: Platform-UI-Inbox <Platform-UI-Inbox>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: P4 CC: gunnar, Tod_Creasey
Version: 3.1Keywords: helpwanted
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Randy Hudson CLA 2005-02-17 11:34:53 EST
Preferences like keybindings and fonts already have scope/context.  Most 
everything else has been left out and only has global scope.  In 3.0, I could 
have separate print margin columns for the default text editor, and the Java 
text editor.  The same for show line numbers, use thick caret, etc. In 3.1, I 
think these scopes have been combined into a single global scope.

Once scoped preferences are modeled, the whole preferences UI should be 
rebuilt to display preferences for a requested scope, instead of "here's 
everything, and here's a grep utility for finding what you need".
Comment 1 Randy Hudson CLA 2005-08-09 12:55:43 EDT
For 3.1, there was a plan item to overhaul preferences/address scalability. I
was under the impression that this meant reorganize preferences by concepts. For
example:

- instead of showing the user every label decorator, show them all preferences
related to CVS. CVS-related preferences are scattered across
General/Appearance/Colors|Decorators, General/Editors, General/Keys,
Perspectives, and of course Team.

- instead of showing the user every keybinding, show them keybindings that are
available in the java source editor, or the global workbench keybindings, etc.

Part of this organization suggests the original request, which is that different
contexts be able to both inherit and override a preference such as "Show Print
Margin".
Comment 2 Tod Creasey CLA 2007-04-03 16:44:34 EDT
This could be done without an API change by using keywords. However we have no plans to work on this feature currently.
Comment 3 Denis Roy CLA 2009-08-30 02:23:53 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.