Community
Participate
Working Groups
Build Identifier: 20100617-1415 The one of the common task for for plug-in development is to configure plug-in options. Currently documentation (http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/preferences_prefs_implement.htm) suggest to do it manualy with defining own constants and overriding initializeDefaultPreferences method of AbstractUIPlugin. But this is well automated task which can be done with visual editor and reduce ammount of typing significantly and will improve refactorings and maintaining the bunch of properties. For example there could be a tab on the plugin.xml visual editor with the title "Properties" where it would be able edit items of the list. Each item has name (valid java identifier), default value, description (will be a comment after generation) and type. Generator can generate not only identifier and initializing of the default values but also typed getter and setter. I understand that this an enchancement and it could become low priority task, but I think it should be done as important IDE task. Probably for JDT project either. Also I should mention that Visual Studio has such feature (I can give more instruction how to see it in action or post screenshots if necessary) and that was the place of inspiration for that task. Reproducible: Always Steps to Reproduce: No reproduce steps
Generating may be simple but refactoring will be a challenge specially when the generated code has been modified.
Having a visual editor for this is a major request and would need strong community involvement to happen. Preferences can be handled in different ways, so the feature would likely be unable to refactor existing settings. A template showing how preference stores could be used might be helpful as well.
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.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.
