| preferences [message #253109] |
Wed, 16 June 2004 13:36 |
 Florian Loitsch
Messages: 26
Registered: July 2009 |
Junior Member |
|
|
hi,
I recently switched from the Plugin#initializeDefaultPluginPreferences()
to the new AbstractPreferenceInitializer-mechanism, and I now have some
small questions:
- why shouldn't I initialize the default-preferences during the
"start(BundleContext context)" of my plugin? (I'm interfacing with
non-java code, and this would reduce the nb of interface-functions.)
- why was the default-preferences-method moved from the plugin-class to
the AbstractPreferenceInitializer-class? In the Preference-class I still
call MyPlugin.getDefault().getPluginPreferences().setDefault(...) , and I
don't know any other way...
- can AbstractPreferenceInitializer#initializeDefaultPreferences() be
called more than once during the lifecycle of a plugin?
- is it bad to get the PreferenceStore of the PlugIn (instead of using
the PluginPreferences directly)? AFAIK the preference-store is backed by
the PluginPreferences anyway.
thanks,
// florian
|
|
|
Powered by
FUDForum. Page generated in 0.03467 seconds
] 
Search
Help
Register
Login
Home
