|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||
See:
Description
| Interface Summary | |
|---|---|
| DependencyRuleApplayable | Description: TODO: patrickb Class Description for DependencyRuleApplayable |
| FormBaseComponentIdProvider | Description: |
| FormDecorator | |
| FormItem | Summary: |
| FormItemContainer | Description: FormContainer and FormComponent -> Composite Pattern Implementors of FormContainer should also extend the olat Container and override its put(.., Component) methods by throwing an exception -> use add instead. |
| FormItemDependencyRule | Description: TODO: patrickb Class Description for FormItemDependencyRule |
| FormLayouter | Description: TODO: patrickb Class Description for FormLayouter |
| FormMultipartItem | Description: |
| Class Summary | |
|---|---|
| FormUIFactory | Factory class to create the flexible form elements. |
Flexi.Form is the way to create forms in OLAT since release 5.2. The following classes and the package elements define a infrastructure and API for the Flexi.Form
FormItemFormItemContainer together with the
FormItem represents the
composite pattern.FormDecorator is
available as $f in velocity pages and wraps an instance of a
FormItem in a velocity container.
It follows the decorator pattern,
although it does not add - but removes functionality of the decorated class.FormItem has a pair of
Component and
ComponentRenderer
to be compatible with the GUI Framework.
The Flexi.Form can be used in two ways - extend the
FormBasicController or
create your own FooBarController, but in this case one has to implement
all form creation stuff itself. It is recommended to use the extending FormBasicController approach.
The impatient may read the
examples and how-tos here to quick start.
Nevertheless the curious people can
find the design decisions here.
For a deeper understanding you may also read the
comparison to the former form infrastructure.
FormEvent).
|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||