SeaMonkey:Toolkit Transition:PrefwindowPanes:HowTo: Difference between revisions

Line 90: Line 90:
               preference="browser.toolbars.showbutton.home"/>
               preference="browser.toolbars.showbutton.home"/>


The <preferences> element must be a direct child of the <prefpane>, with the <preference>s as its children. Each <preference> needs the attributes ''name'' (with the name of the preference in ''prefs.js'' etc.) and ''type'' with its type, see [http://developer.mozilla.org/en/docs/Preferences_System:preference MozDev for details]. Since preference names are unique by default, the ''id'' attribute should be set to the pref name as well.
The <preferences> element must be a direct child of the <prefpane>, with the <preference>s as its children. Each <preference> needs the attributes ''name'' (with the name of the preference in ''prefs.js'' etc.) and ''type'' with its type, see [http://developer.mozilla.org/en/docs/Preferences_System:preference DevMo for details]. Since preference names are unique by default, the ''id'' attribute should be set to the pref name as well.


The former ''prefstring'' attribute on an element must be replaced by a ''preference'' attribute, which contains the ''id'' of the respective <preference>.
The former ''prefstring'' attribute on an element must be replaced by a ''preference'' attribute, which contains the ''id'' of the respective <preference>.


All reading/writing of preferences is handled by the backend, there is usally no need to instantiate preference interface/service!
All reading/writing of preferences is handled by the backend, there is usally no need to instantiate preference interface/service!
235

edits