Community
Participate
Working Groups
In our application we distinguish between two kinds of plugins: - plugins with a graphical user interface (ui-plugins) and - plugins without a graphical user interface (model-plugins). It is possible to have more than one ui-plugin for a model-plugin (we need this to provide customer specific ui configurations). Our model-plugins defining preferences. The ui-plugins than provide the preference pages to specify the installation specific preference values. To use preference pages that are subclasses of org.eclipse.jface.preference.PreferencePage an IPreferenceStore is needed. Our idea was that the plugin that defines the preferences (that is the model- plugin) provides the preference store too. If you want to do this the model- plugins have to depend from org.eclipse.jface, but in our opion this is not right because a model plugin does not have an ui but jface is an ui-component. Our suggestion is to move IPreferenceStore to org.eclipse.core.runtime and than move the inner class CompatibilityPreferenceStore from AbstractUIPlugin to Plugin.
Core already has the Preferences class that instances of Plugin have access to should you need it. The IPreferenceStore was implemented beforehand and needs to be merged with the Core story at some point. I am going to mark this as a duplicate of the plan item for 3.0 Bug 36965 so that you can contribute to the discussion there. *** This bug has been marked as a duplicate of 36965 ***
