TWiki::Form
Object representing a single form definition.
$form
- topic name to read form definition from
May throw TWiki::OopsException
$web
the web of the topic being rendered
$topic
the topic being rendered
$meta
the meta data for the form
$useDefaults
if true, will use default values from the form definition if no other value is given
Render the form fields for entry during an edit session, using data values from $meta
$fieldDef
the field being rendered
$web
the web of the topic being rendered
$topic
the topic being rendered
$value
the current value of the field
Render a single form field for entry during an edit session, using data values from $meta. Plugins can provide a handler that extends the set of supported types
SMELL: this should be a method on a field class SMELL: JSCalendarContrib ought to provide a 'date' handler.
$useDefaults
if true, will use default values from the form definition if no other value is given
Render form fields found in the meta as hidden inputs, so they pass through edits untouched.
$query
- the query
$metaObject
- the meta object that is storing the form values
$initialiseMissing
- if true, will cause fields that are in the form but have no value in the query or in the meta to be initialised to ''.
For each field, if there is a value in the query, use it. Otherwise if there is already entry for the field in the meta, keep it.
Returns the number of fields which had values provided by the query, and a references to an array of the names of mandatory fields that were missing from the query.
$name
- name of a form field (value of the name
attribute)
If the form does not define the field, it is assumed to be mergeable.
$name
- name of a form field (value of the name
attribute)
$templates
ref to templates singleton
$meta
- meta object containing the form to be rendered
SMELL: Why? Is reading the form topic such a big burden?