Versions Compared

Old Version 10

changes.mady.by.user Justin Obara

Saved on

compared with

New Version Current

changes.mady.by.user Anastasia Cheetham

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

NameDescriptionValuesDefault

prefsEditorType

(Optional) The string name of a grade of preference editor.

The Preferences Framework provides three built-in types of editor:

"fluid.prefs.separatedPanelPrefsEditor"
"fluid.prefs.fullNoPreview"
"fluid.prefs.fullPreview"

Integrators can use one of these grades, or define their own grade, using one of these grades as a base grade.

"fluid.prefs.separatedPanelPrefsEditor"
storeType(Optional) The string name of a grade of a Settings Store.

Integrators can define their own store grade by using the built-in default grade "fluid.globalSettingsStore" as a base grade.

"fluid.globalSettingsStore"
enhancerType(Optional) The string name of a grade of a UI Enhancer.Integrators can define their own enhancer grade by using the built-in default grade "fluid.pageEnhancer" as a base grade."fluid.pageEnhancer"
templatePrefix
(Optional) A string value representing the relative path to the directory containing the templates. This value will overwrite the templatePrefix value supplied by auxiliary schemas.  
messagePrefix
(Optional) A string value representing the relative path to the directory containing the message files. This value will overwrite the messagePrefix value supplied by auxiliary schemas.  
prefsEditor
(Optional) The data structure that configures the prefsEditor component. See Preferences Editor for what is accepted in the data structure.  
enhancer
(Optional) The data structure that configures the uiEnhancer component. See UI Enhancer for what is accepted in the data structure.  
store
(Optional) The data structure that configures the store component. See Settings Store for what is accepted in the data structure.  
listeners
(Optional) A data structure defining listener functions for supported events. See Infusion Event System for more information about registering event listeners.

The Preferences Framework supports one event:

onReady: Fires after the preferences editor is rendered and ready to use.

 

Usage

The simplest way to create a separated panel preferences editor is to provide the primary and auxiliary schema using the options:

Code Block
var prefsEditor = fluid.prefs.create("#myPrefsEditor", {
    build: {
        primarySchema: {...},
        auxiliarySchema: {...}
    }
});

...