Forms (as of release 1.11)

1. Introduction

Due to the fact, that the page controller of the APF provides a generic frame to handle taglibs, we were able to implement a form abstraction built on taglibs (e.g. text fields).

The release of the adventure php framework contains a set of taglibs, that fully describe HTML forms and that contain features such as filtering, validation and presetting at the same time out of the box. With the taglibs reworked with release 1.11, form fields can be applied various filters and validators and custom form elements can be integrated with the delivered ones.

The subsequent chapters describe the general design and the handling of APF forms as well as the tags shipped with the release with their meaning and functionality. Reading this documentation and implementing applications, it is recommended to have the API documentation opened. There, you can see, which functionality is included in the various taglibs - e.g. the html_taglib_form.

2. Construction of forms

As noted in the introduction, APF forms are represented by taglibs. The <html:form /> tag forms the base taglib, that encapsulates all other form tags and presents an APF form as a single object to the document controller. It contains further tag instances as it's child oblects that represent dedicated elements like text fields or buttons or functional tags such as place holders, listeners or tags, that add custom form controls.

Forms - as you know from other APF GUI elements - are defines within template files. A simple form with a search field and a button looks like this: In order to display the form a document controller must be defined for the corresponding template. This is necessary, because a form - in contrast to other tags - is always coupled with functionality to handle the data passed to the form. This may be reading the search term or executing the search or saving user data.

Displaying a form is not rocket science with the APF and can be done with the following controller code: The subsequent sections present the form controls contained within the APF release and give you a brief introduction to the usage of these elements.

3. Shipped tags

The APF contains an extended set of form control abstraction tags, that can be configured for different purposes. In case this is not enough, custom form taglibs can be introduced as desired. This is described in detail under usage of forms.

Since the APF's page controller is built up on a generic tag parser, form tags can be added generic attributes such as:

• id="..."
• class="..."
• style="..."

These are presented in the generated source code and can thus be used for formatting purposes. For this reason, the following chapters do not mention these attributes, but only describe the attributes, that are necessary for the configuration of the tag.


The form tag itself takes three functional atributes, that are used for definition and configuration: Description of the attributes:

• name: Name of the form. This attribute is used to address the form within a document controller. (Allowed characters: [A-Za-z0-9-_])
• method: Method that is used to send the form data. By default, post is used. (Allowed characters: [get|post])
• action: The url, that is called on button click by the browser.

3.1. Button

This taglib represents a submit button. APF form elements are validated and filtered on button click event. Hence, it is necessary to specify a button or image button within the form, due buttons create the click event. Description of the attributes:

• name: Name of the button. The name is used to access the button. This is necessary for validators and filters. (Allowed characters: [A-Za-z0-9-_])
• value: Value of the button. The browser uses this value to label the button.

3.2. Image button

The image button tag creates an image button, that uses an image as the label. The functionality is equal to the "normal" button. Description of the attributes:

• name: Name of the button. The name is used to access the button. This is necessary for validators and filters. (Allowed characters: [A-Za-z0-9-_])
• src: Image source.

3.3. Reset button

As of the release 1.10, the form taglibs contain a reset button wrapper. It represents a HTML reset button and can be addressed and configured as "normal" buttons within a document controller.

Description of the attributes:

• value: The value (label) of the reset button.

3.4. Hidden field

Description of the attributes:

• name: The name of the hidden field. This attribute can be used to access the control. (Allowed characters: [A-Za-z0-9-_])
• value: The value of the hidden field.

3.5. Text field

Description of the attributes:

• name: Name of the text fields. This attribute can be used to access the control. (Allowed characters: [A-Za-z0-9-_])
• value: Value of te text field.

3.6. Text area

You can use the APF text area wrapper taglib in two flavours: without explicit content as a self-closing tag and with content as explicitly closing tag. Description of the attributes:

• name: Name of the text area. This attribute can be used to access the control. (Allowed characters: [A-Za-z0-9-_])

3.7. Password field

Description of the attributes:

• name: Name of the password field. This attribute can be used to access the control. (Allowed characters: [A-Za-z0-9-_])
• value: Value of the password field.

3.8. File upload field

Description of the attributes:

• name: Name of the file upload field. This attribute can be used to access the control. (Allowed characters: [A-Za-z0-9-_])

3.9. Checkbox

The checkbox implementation is not only a simple wrapper for the HTML checkbox, but includes the functionality to automatically check or uncheck the box. With this taglib, the problem with re-checking boxes on re-submit is solved. Description of the attributes:

• name: Name of the checkbox. This attribute can be used to access the control. (Allowed characters: [A-Za-z0-9-_])
• value: Value of the checkbox.
• checked: Defines, whether the checkbox should be preselected.

3.10. Radio button

The radio button implementation is not only a simple wrapper for the HTML radio buttons, but includes the functionality to automatically check or uncheck the button. With this taglib, the problem with re-checking buttons on re-submit is solved. Description of the attributes:

• name: Name of the radio button. This attribute can be used to access the control. (Allowed characters: [A-Za-z0-9-_])
• value: Value of the radio button - or precisely - the name of the current option.
• checked: Defines, whether the button should be preselected.

3.11. Select field

A select field can be defined in two different ways. Possibility one is a field, that is filled dynamically within a document controller and does not contain static options. Possibility two is a select field, that defines static options that may be preselected. Description of the attributes:

• name: Name of the select field. This attribute can be used to access the control. (Allowed characters: [A-Za-z0-9-_])
• value: Value of the option. (Allowed characters: [A-Za-z0-9-_])
• selected: In case an option should be preselected, the selected attribute must contain the name of the attribute as it's value.

3.12. Multi select field

As the simple select field, the multi select field allows you to specify two different types: with and without static options. Description of the attributes:

• name: Name of the multi select field. This attribute can be used to access the control. (Allowed characters: [A-Za-z0-9-_])
• value: Value of the option. (Allowed characters: [A-Za-z0-9-_])
• selected: In case an option should be preselected, the selected attribute must contain the name of the attribute as it's value.

3.13. Place holder

A place holder can be used to insert dynamic content into the form. Description of the attributes:

• name: Name of the place holder. This attribute can be used to access the control. (Allowed characters: [A-Za-z0-9-_])

Filling a place holder, the html_taglib_form's method setPlaceHolder() can be uses:

3.14. Date control

To ease date select field generation, the APF contains a date form control that can be configured to fit your needs. Description of the attributes:

• name: Name of the date control. This attribute can be used to access the control. (Allowed characters: [A-Za-z0-9-_])
• yearrange: The range of years, that should be presented to the user. Example: 1990-2007. (Allowed characters: [0-9-])
• offsetnames: Explicitly specifies the name of the date control's components (=name of the single fields). Example: day;month;year. (Allowed characters: [A-Za-z;])

3.15. Marker

As described in chapter dynamic forms, the <form:marker /> tag can be used to position dynamic form elements. The tag itself creates no output. Description of the attributes:

• name: Name of the markers. This attribute can be used to access the control. (Allowed characters: [A-Za-z0-9_-])

3.16. Addtaglib

The <form:addtaglib /> tag is the pendant to the <core:addtaglib /> tag. It offers the possibbility to add custom form tags. Description of the attributes:

• namespace: Namespace path seperated with "::". (Allowed characters: [A-Za-z0-9_-:])
• prefix: XML prefix (Allowed characters: [a-z])
• class: XML class (Allowed characters: [a-z])

3.17. Getstring

The <form:getstring /> tag offers the possibility to display language dependent values from a language dependent config file within forms. Details on the configuration can be read about in the chapter, that describes the <html:getstring /> tag. Description of the attributes:

• namespace: Namespace of the configuration file. (Allowed characters: [A-Za-z0-9_-:])
• config: Name of the configuration file. (Allowed characters: [A-Za-z0-9-_])
• entry: Name of the configuration key to display the value of. (Allowed characters: [A-Za-z0-9-_.])

3.18. Listener

The listener tag is part of the new validation concept. The tag "listens" on the event, the validator fires and shows it's content, in case the addressed form element could not be validated successfully. Within the body of the tag, several subtags and textual content can be defined, that can be used to format the output. Details on the validation concept can be read about in chapter 4. Description of the attributes:

• control: Name of the form element, that the validator tag listens to. (Allowed characters: [A-Za-z0-9_-])
• name: Name of the listener. This attribute can be used to access the control. (Allowed characters: [A-Za-z0-9_-])

The place holder tag <listener:placeholder /> acts like the <html:placeholder />, the <listener:getstring /> tag like the <html:getstring /> tag. In order to fill the the place holder, the following document controller code can be used:

Template: Controller:

3.19. Display of form errors

The tag described within chapter 3.18 can be used to automatically display field relevant errors. The <form:error /> tag is used to display errors for the matter of the whole form. If one of the fields could not be validated successfully, the content of the tag is displayed - if present in the form definition. The place holder tag <error:placeholder /> acts like the <html:placeholder />, the <error:getstring /> tag like the <html:getstring /> tag. Filling the place holder can be done as described in the last chapter.

3.20. Display of form success messages

The tag described within chapter 3.19 can be used to automatically display error messages for the matter of the whole form. Often, it is necessary to display messages in case the form was correctly filled. The <form:success /> displays it's content, in case all fields are maked valid. The definition of the tag is as follows: The place holder tag <success:placeholder /> acts like the <html:placeholder />, the <success:getstring /> tag like the <html:getstring /> tag. Filling the place holder can be done as described in the last chapter.

4. Validation

In the previous versions of the APF the validation was linked directly with a form element and the validation was executed within the lifecycle of the taglibs. This has the disadvantage, that one element can be defined with only one validator. This leads to redundant code, because each field must have it's own validator defined. Furthermore, it was not possible to implement own validators.

From version 1.11 these circumstances were considered and the form taglibs were moved to a new variation of the validation. From this version validators are applied by an own tag, that follows the observer pattern. The tag itself then binds a validator to the desired form control. Thus it is possible to attach several validators onto one field, to write own validators and to validate several fields with one observer definition at the same time.

The definition of a validator now is as follows: Description of the attributes:

• namespace: Namespace of the validator implementation. (Allowed characters: [A-Za-z0-9:])
• class: Name of the validator implementation (name = class name!) (Allowed characters: [A-Za-z0-9_])
• button: Name of the button, that triggers the validation event. The validation is executed, when the isSent event is fired by a button or an image button. (Allowed characters: [A-Za-z0-9-_])
• control: Name of the form control to validate. In case, multiple controls should be allocated the same validator by only one tag definition, the attribute can contain a pipe-separated list of form controls (e.g. sender|recipient|subject). (Allowed characters: [A-Za-z0-9-_|])

4.1. Shipped validators

As in previous releases, the APF shipps a couple of built-in validators. These usually cover the large part of the demands. Should these not be enough, own validators can be implemented. This is described in the next chapter.

Currently the following validators are available:

4.1.1. TextLengthValidator

The TextLengthValidator checks a text form field (text field, password field, text area) whether the contained text has a least length. By default, the text entered by the user must have a least length of 3 characters, before the field is considered valid. Provided that another text length is desired, the attribute minlength must be given in the attribute list of the referenced text field: Within the code block the form control firstname is tested to contain at least >=3 characters, the lastname field must contain at least 5 characters to be valid.

4.1.2. NumberValidator

The NumberValidator checks whether a text field contains a valid number. For this reason, the PHP function is_numeric() is used.

4.1.3. EMailValidator

The EMailValidator checks whether the referenced form control contains a valid email address. For this reason, the content of the text field is checked against a regular expression.

4.1.4. PhoneAndFaxValidator

The PhoneAndFaxValidator checks whether a form field contains a valid phone or fax number. For this reason, the content of the text field is checked against a regular expression.

4.1.5. FieldCompareValidator

With the FieldCompareValidator you are enabled to compare the content of two text fields. If the content of both controls is equal, the fields ara makred valid.

Due to the fact, that an APF form validator must be added to one dedicated control (due to observer implementation), the main control must define the reference on the control, that can be used to double check the content. For this reason, the ref attribute within the main control definition must refer to the field, that is defined for the comparison check.

4.1.6. FolderValidator

The FolderValidator belongs to the group of text field validators. It checks, whether a text field contains a valid folder path.

4.1.7. SimpleBirthdayValidator

The SimpleBirthdayValidator is also belonging to the group of text field validators and checks the content of a text field to contain a date definition that matches the pattern dd.MM.YYYY.

4.1.8. DefaultSelectFieldValidator

The DefaultSelectFieldValidator can be added to select fields. It checks, if the selected content is not empty (=no option selected). Please note, that this validator may only be used with select fields, that are defined statically (with an explicit set of options). To validate dynamic select fields, please use the SimpleSelectControlValidator.

4.1.9. SimpleSelectControlValidator

The SimpleSelectControlValidator validates static and dynamic text fields (=options are filled within a document controller). The validator checks, if the selected content is not empty.

4.1.10. MultiSelectFieldValidator

The MultiSelectFieldValidator is the pendant to the SimpleSelectControlValidator but validates multi select fields. It checks the target element to have at least one option selected.

4.1.11. SimpleRadioControlValidator

Using the SimpleRadioControlValidator, a radio button as well as a radio button group can be checked. The validator thus expects, that at one button out of a group is selected. The validator can be used for static and dynamic form definitions.

4.1.12. SimpleDateControlValidator

The SimpleDateControlValidator validates the date control described in chapter 3.14. It requires the date to be greater or equal to today's date..

4.2. Construction of validators

Validators are classes, that are derived from AbstractFormValidator. This abstract base class defines the structure of all form validators. This is necessary to be able to apply all validators to form controls as an observer.

The interface is as follows: The constructor takes the control to validate and the button that triggers the element as arguments. The validate() method is applied the content to check against the logic the validator includes. The return param is expected to be of type boolean indicating successful validation (true) of failure (false).

The method notify() is called, when a form control could not be validated successfully. It is intended to add css formatting to the desired form control, to fill place holders or to apply changes to the DOM tree. In common, within this function the form fields are maked as invalid using css style definitions and the listeners are notified.

The class members $__Control and $__Button contain the instance of the form control to validate and the button, that is used as a trigger for the validation event. Thus, these can easily be used within the validation code.

To be able to add a validator as an observer to a form control, the form control, must support this operation. For this reason, each form element must implement the addValidator() function. The signature of this method is defined within form_control: As the code snippet describes, the method takes an instance of the validator as an argument. In case, the validator is active (=button is clicked) the validator is executed and on failure, the notify() methode is called.

Further, the validator by default is passed the value of the tag, what is only legal for text fields. Thus, non-text fields re-implement the method to pass the right content to the validator.

4.3. Implementation of validators

As mentioned in the last chapters, a validator must inherit from the AbstractFormValidator class. Besides, the APF includes two more base classes, that can be used to implement text field or select box validators:

• TextFieldValidator: Base class for all text field validators
• SelectFieldValidator: Base class for all select box validators

These include the functionality to mark the desired form elements as invalid and notify the validation event listeners.

In order to implement custom validators, please remember the following topics:

• Each validator must inherit from the AbstractFormValidator class.
• The method markAsInvalid() can be used to mark a form element as invalid.
• The method markAsInvalid() can be used to inform validation listeners.
• Using the button's isSent() method, you can decide, whether the form was sent or not.

5. Filters

In the previous versions of the APF the filters were linked directly with a form element and executed within the lifecycle of the taglibs. This has the disadvantage, that one element can be defined with only one filter. This leads to redundant code, because each field must have it's own filter defined.

From version 1.11 these circumstances were considered and the form taglibs were moved to a new variation of the filter facility. Thus, filters can be added as observers just like form validators can be defined.


The definition of a filter now is as follows: Description of the attributes:

• namespace: Namespace of the tilter implementation. (Allowed characters: [A-Za-z0-9:])
• class: Name of the tilter implementation (name = class name!) (Allowed characters: [A-Za-z0-9_])
• button: Name of the button, that triggers the filter event. Filtering is executed, when the isSent event is fired by a button or an image button. (Allowed characters: [A-Za-z0-9-_])
• control: Name of the form control to filter. In case, multiple controls should be allocated the same filter by only one tag definition, the attribute can contain a pipe-separated list of form controls (e.g. sender|recipient|subject). (Allowed characters: [A-Za-z0-9-_|])

5.1. Available filters

As in previous releases, the APF shipps a couple of built-in filters. These usually cover the large part of the demands. Should these not be enough, own filters can be implemented. This is described in the next chapter.

Currently the following filters are available:

5.1.1. EMailFilter

The EMailFilter removes all characters, that must not be contained in a valid email address.

5.1.2. NoSpecialCharactersFilter

The NoSpecialCharactersFilter filters all characters, that to not comply with the regexp [^0-9A-Za-z-_\.& ].

5.1.3. OnlyHTMLEntitiesFilter

Using the OnlyHTMLEntitiesFilter you can encode all special characters into their HTML entity. Please note, that this filter may generate multiple encoding.

5.1.4. OnlyIntegersFilter

The OnlyIntegersFilter only returns the numbers contained in the given text.

5.1.5. OnlyLettersFilter

The OnlyLettersFilter removes all signs except normal characters.

5.1.6. OnlyNumbersFilter

The OnlyNumbersFilter only allows numbers and formatting signs such as dots or commas.

5.1.7. SpecialCharacterFilter

The SpecialCharacterFilter filters all signs except normal characters and signs that are needed for normal sentences.

5.1.8. String2LowerFilter

The String2LowerFilter converts all characters to lowercase letters.

5.1.9. String2UpperFilter

The String2UpperFilter converts all characters to uppercase letters.

5.1.10. StripTagsFilter

Using the StripTagsFilter all HTML and PHP code fragments are filtered out. This is especially good for text areas.

5.2. Construction of filters

Form filters are special filters, that are built on the APF filter API described in detail in chapter design and function of filters. Each form filter must implement the AbstractFormFilter class that acts as an interface for dedicated form filter implementations.

Just like the form validators, form filters must implement some form-specific methods. The AbstractFormFilter interface class is as follows: The constructor takes the control to filter and the button that triggers the element as arguments. The filter() method is applied the content to filter included in the method. The return param is expected to be the filtered content.

isActive() returns true in case the filter should be executed and false otherwise.

The class members $__Control and $__Button contain the instance of the form control to filter and the button, that is used as a trigger for the validation event. Thus, these can easily be used within the filter code.

To be able to add a filter as an observer to a form control, the form control, must support this operation. For this reason, each form element must implement the addFilter() function. The signature of the method defined within the form_control class is as follows: As the code snippet describes, the method takes an instance of the filter as an argument. In case, the filter is active (=button is clicked) the filter is executed.

Further, the filter is passed the content of the value attribute of the form control by default. Thus, non-text fields re-implement the method to pass the right content to the filter.

5.3. Implementation of filters

As mentioned in the last chapters, a filter must inherit from the AbstractFormFilter class.

In order to implement custom filters, please remember the following topics:

• Each filter must inherit from the AbstractFormFilter class to be compatible with the APF filter API.
• The isSent() method can be used to query the click status of a given button within the desired form.
• The isActive() can be used to check, whether a filter is active or not. In most cases, the implementation defined within the AbstractFormFilter can be used without adaption.

6. Usage of forms

Chapter usage of forms deals with the usage of APF forms and the form handling using document controller. The present page is only intended as a reference for the shipped tags and the implementation of validators and filters. Further, the linked chapter discusses dynamic form implementation.

Comments

QUICKNAVI

• All releases
• Roadmap
• Subversion repository
• Bugtracking
• Why APF?
• Articles
• Wiki
• RPM Installation HOWTO
• Partner sites
• APF auf SourceForge.net

• Imprint
• Contact
• Privacy policy
• Legal notice
• Security
• License

Adventure PHP Framework (APF) is a product developed by the APF Developer Team. It's released under the GNU Lesser General Public License (LGPGL)
Commercial use is permitted.

Copyright © 2009 Adventure PHP Framework
All textual content on this site is protected by Copyright Law and may be used under the Terms of the GNU Free Documentation License (GNU FDL) See Legal notice for more information.