acme
, and a namespace different from http://www.acme.com/xbl
.acme:form-settings
refers to the XBL component implementing the custom tab:acme
is the prefix you have mapped with the oxf.xforms.xbl.mapping.acme
property aboveform-settings
is the name you give your XBL component (it doesn't have to be form-settings
)fb-initialize
is dispatched to initialize the tab when the dialog shows.fb-apply
is dispatched to save the settings, if any, to the form definition.fb-initialize
and fb-apply
both take the following parameters:form
element(xh:html)
form-instance
element(form)
form-metadata
element(metadata)
acme:control-settings
refers to the XBL component implementing the custom tab:acme
is the prefix you have mapped with the oxf.xforms.xbl.mapping.acme
property abovecontrol-settings
is the name you give your XBL component (it doesn't have to be control-settings
)control-settings.xbl
, an example of custom Control Settings that lets form authors enter, for each control, a "question identifier", which value is stored in an attribute of the form data, on the element corresponding that corresponds to the current control.acme:form-settings
.fb-initialize
is dispatched to initialize the tab when the dialog shows.fb-apply
is dispatched to save the settings, if any, to the form definition.fb-initialize
and fb-apply
both take the following parameters:form
element(xh:html)
form-instance
element(form)
form-metadata
element(metadata)
data-holders
element()*
fb-initialize
takes the following parameters:original-control-id
xs:string
first-name-control
original-control-name
xs:string
first-name
fb-apply
takes the following parameters:control-name
xs:string
first-name
fb-initialize
and fb-apply
, the control name (and id) might have been changed in the dialog by the user. The original-control-name
and control-name
parameters reflect that change when needed.