|
The default type of form could be construed as an equivalent
to the HTML form. In general dWebSpec forms are means of grouping elements.
The types are described below
aggregator
This is used to group together elements for the purpose of specification.
It does not necessarily have any translation to physical implementation; it is
a means of grouping elements together for the purpose of common specifications.
An element could appear within multiple aggregations. Any specification with
the aggregator sub-form would complement or override those in the parent form,
as appropriate.
component
This type, allows the aggregation of elements within a
component. In dWebSpec, a component could be shown as an element within a form.
The binding and events involved could be handled on the component level.
However, to provide specifications for its constituent elements, further
elaboration must be provided with a Form Descriptor of the component type. It
is within the latter that the specifications on the constituent elements could
be provided.
form-static
form-active (default)
form-active-in
form active-out
As indicated above, the standard form type of the
Form Descriptor represents the HTML form. However, these could be split
further into categories, based on the server-side activities.
The form-static type simply implies that the
controller does not process the elements in the form, or there are no active
binding to controller held objects.
form-active indicates that the form is recognized and
the controller is used for processes at least one element on the form. This
could involve simple value binding, but could also involve usage of controller
services like validation, formatting and conversion.
form-active-in would imply that the controller could
participate in the rendering of the form, whereas providing no services when
the form is submitted, or out-going. An example of this would be a form in an
application that is to be submitted to associate web site. Despite the
participation in the provision of the user identity and for other purposes on
the page, the final handling of this form, on submission, would be by the
associate web site.
form-active-out would imply that the controller would
not participate in the rendering of the form; however, the controller would
take part in the handling of the submitted form. An example of this is a page
that is used to register users. Initially a static page would be presented with
all the entry fields blank. When the user complete these entry and press the
submit button, the controller would then process the form.
|
Technologies
