Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "FAQ How do I load and save plug-in preferences?"

Line 27: Line 27:
 
The above technique has been deprecated since 3.1.
 
The above technique has been deprecated since 3.1.
  
IPreferencesService service = Platform.getPreferencesService();
+
Sadly, this author has no clue as to how to set preferences in a way that can actually be read.
Preferences prefs = service.getRootNode().node("my.plugin.id");
+
+
if (storing) {       
+
  prefs.put(SOME_KEY, someValue);
+
} else {
+
  someValue = prefs.get(SOME_KEY, "default value" );
+
}
+
 
+
<tt>org.osgi.service.prefs.Preferences</tt> support <tt>int, long, boolean, byte[], float,</tt> and <tt>double</tt> as well as the above <tt>String</tt> example.
+
 
+
The above example is a tad unrealistic in that it uses <tt>storing</tt> as an excuse to show both <tt>get()</tt> and <tt>set()</tt>.  Normally these could be called from within a plugin's <tt>start()</tt> and <tt>stop()</tt> overrides instead.
+
 
+
 
+
  
 
== See Also:  ==
 
== See Also:  ==

Revision as of 12:58, 19 July 2010

The Deprecated Way

Each plug-in has a local workspace preference store for saving arbitrary primitive data types and strings. Preferences displayed in the Workbench Preferences dialog are typically stored in these local plug-in preference stores. The Import and Export buttons in the Workbench Preferences page also operate on these plug-in preference stores.

Retrieving values from plug-in preferences is fairly straightforward:

   Plugin plugin = ExamplesPlugin.getDefault();
   Preferences prefs = plugin.getPluginPreferences();
   int value = prefs.getInt("some.key");

When preferences are changed, the preference store must be explicitly saved to disk:

   prefs.setValue("some.key", 5);
   plugin.savePluginPreferences();

The plug-in preference store can also store default values for any preference in that plug-in. If a value has not been explicitly set for a given key, the default value is returned. If the key has no default value set, a default default value is used: zero for numeric preferences, false for Boolean preferences, and the empty string for string preferences. If the default default is not appropriate for your preference keys, you should establish a default value for each key by overriding the initializeDefaultPluginPreferences method in your Plugin subclass:

   protected void initializeDefaultPluginPreferences() {
      prefs = plugin.<strike>getPluginPreferences</strike>();
      prefs.setDefault("some,key", 1);
   }

Although you can change default values at any time, it is generally advised to keep them consistent so that users know what to expect when they revert preferences to their default values. Programmatically reverting a preference to its default value is accomplished with the setToDefault method.


Current Practice

The above technique has been deprecated since 3.1.

Sadly, this author has no clue as to how to set preferences in a way that can actually be read.

See Also:


This FAQ was originally published in Official Eclipse 3.0 FAQs. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the Eclipse Public License v1.0.

Back to the top