Paloose Forms
The Paloose Forms (PForms) framework is loosely based on JXForms (now deprecated) which in turn was based on XForms. There are sufficient differences with PForms to make the latter to be of only loose help. It is worth reading the FAQ entry on flows for some background information on why Paloose Forms do not use CForms.
The use of PForms is described elsewhere, this page just gives the PForm elements.
Basic Structure
A Paloose form is enclosed by the <form> in the namespace "http://www.paloose.org/schemas/Forms/1.0":
where:
- id — the identity of this form (used mainly in the CSS,
- flow — the flow being used,
- continuation — the continuation identity used to navigate the flow,
- session — the current flow session id.
For more explanation of these see the PForms example. Within the form structure there are a set of items that reflect the various components within a form.
Simple Input Field (Input).
Input fields contain a single line entry field (cf HTML <input> input field). It has the following example structure:
where the attributes are:
- ref — how the flowscript references this field,
- class — the id for the CSS style.
Simple Password Field (secret).
Secret fields are identical to input fields except that text entered only displays as "*". They have identical structure to input fields:
where the attributes are:
- ref — how the flowscript references this field,
- class — the id for the CSS style.
Hidden Field (hidden).
Hidden fields allow the transmission of information that is hidden from the user. The only enclosed data is the initial value:
where the attributes are:
- ref — how the flowscript references this field,
Output Field (output).
Output fields allow display of data to the user in a read-only field for giving the user information. For example the following would display the value of the flow variable username:
where the attributes are:
- ref — how the flowscript references this field,
Form button (submit).
Submit entries define how the form is treated, for example would produce an HTML form button:
where the attributes are:
- ref — how the flowscript references this field,
- class — the id for the CSS style.
Multiple Select Fields.
When it is required to select several of a set of choices the multiple select is used. This is the equivalent of the checkbox HTML form field. Each choice is entered as a set of fields
where the attributes are:
- ref — how the flowscript references this field,
- appearance — the style of the multiple selection. full denotes a set of checkboxes, and compact is a multiple selection list. If appearance is omitted then compact is assumed.
- checked — whether the checkbox is checked at page load time. If checked is omitted then false is assumed.
For example:
would display as:
while a compact version would display as:
Single Select Fields.
When it is required to select several of a set of choices the multiple select is used. This is the equivalent of the checkbox HTML form field. Each choice is entered as a set of fields
where the attributes are:
- ref — how the flowscript references this field,
- appearance — the style of the mutiple selection. full denotes a set of checkboxes, and compact is a multiple selection list.
For example:
would display as:
Text Area
text area fields allow multi-line
where the attributes are:
- ref — how the flowscript references this field,
For example:
Label Field
Label fields contain text that is associated with the field. For example:
which would typically output
Value Field
Value fields contain predefined data that is loaded into the field when the page is first displayed. For example:
would put the text "Please enter username" into the field when the page is loaded. If the PXTemplateGen is used then it is possible to use sitemap variables, for example:
Hint Field
Hint field contains text that is output when the cursor is hovered above the field. For example:
Violations Field
Violations fields are empty place holders used when continuations require to report. Any tags within here will be ignored. For example: