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.
Difference between revisions of "FAQ How do I use the preference service?"
m |
|||
| Line 12: | Line 12: | ||
depend on the given scope. For example, the instance and default | depend on the given scope. For example, the instance and default | ||
scopes use a plug-in ID as a qualifier. The project scope uses | scopes use a plug-in ID as a qualifier. The project scope uses | ||
| − | two qualifiers: the project name and the plug-in | + | two qualifiers: the project name and the plug-in ID. Thus, the fully qualified path of a preference node for the FAQ Examples plug-in in the workspace project <tt>My Project</tt> would be |
| − | ID. Thus, the fully qualified path of a preference node for the | + | |
| − | FAQ Examples plug-in in the workspace project | + | |
| − | <tt>My Project</tt> would be | + | |
<pre> | <pre> | ||
/project/My Project/org.eclipse.faq.examples | /project/My Project/org.eclipse.faq.examples | ||
</pre> | </pre> | ||
| − | |||
| − | |||
| − | |||
Below the level of scopes and scope contexts, the preference tree can | Below the level of scopes and scope contexts, the preference tree can | ||
| Line 29: | Line 24: | ||
to create hierarchies of preference nodes for storing hierarchical preference | to create hierarchies of preference nodes for storing hierarchical preference | ||
data. | data. | ||
| − | |||
| − | |||
| − | |||
Lookups in this global preference tree can be done in a number of ways. If | Lookups in this global preference tree can be done in a number of ways. If | ||
| Line 47: | Line 39: | ||
for a given project. They can also be stored at the instance scope to | for a given project. They can also be stored at the instance scope to | ||
specify preferences that apply to all projects in a workspace. | specify preferences that apply to all projects in a workspace. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== See Also: == | == See Also: == | ||
| − | + | *[[FAQ_What_is_a_preference_scope%3F]] | |
| − | + | ||
| − | [[FAQ_What_is_a_preference_scope%3F]] | + | |
<hr><font size=-2>This FAQ was originally published in [http://www.eclipsefaq.org Official Eclipse 3.0 FAQs]. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the [http://www.eclipse.org/legal/epl-v10.html Eclipse Public License v1.0].</font> | <hr><font size=-2>This FAQ was originally published in [http://www.eclipsefaq.org Official Eclipse 3.0 FAQs]. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the [http://www.eclipse.org/legal/epl-v10.html Eclipse Public License v1.0].</font> | ||
Latest revision as of 22:05, 29 May 2006
In addition to the plug-in preferences for the local workspace obtained via Plugin.getPluginPreferences, a preference service new in Eclipse 3.0 can be used to store preferences in different places. This facility is similar to the Java 1.4 preferences API. Each preference object is a node in a global preference tree. The root of this preference tree is accessed by using the getRootNode method on IPreferenceService. The children of the root node represent different scopes. Each scope subtree chooses how and where it is persisted: whether on disk, in a database, or not at all. Below the root of each scope are typically one or more levels of contexts before preferences are found. The number and format of these contexts depend on the given scope. For example, the instance and default scopes use a plug-in ID as a qualifier. The project scope uses two qualifiers: the project name and the plug-in ID. Thus, the fully qualified path of a preference node for the FAQ Examples plug-in in the workspace project My Project would be
/project/My Project/org.eclipse.faq.examples
Below the level of scopes and scope contexts, the preference tree can have further children for storing hierarchies of information. This is analogous to the org.eclipse.ui.IMemento facility used for persisting user-interface states. With the new preference mechanism, it is very easy to create hierarchies of preference nodes for storing hierarchical preference data.
Lookups in this global preference tree can be done in a number of ways. If you know exactly which scope and context you are looking for, you can start at the root node and navigate downward using the node methods. Each scope typically also provides a public class for obtaining preferences within that scope. For example, you can create an instance of ProjectScope on an IProject to obtain preferences stored in that project. Finally, the preference service has methods for doing preference lookups that search through all scopes. This can be used when you allow users to specify what scope their preferences are stored at and you want more local scopes to override values in more global scopes. For example, JDT compiler preferences can be specified at the project scope if you want to override preferences for a given project. They can also be stored at the instance scope to specify preferences that apply to all projects in a workspace.
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.