Difference between revisions of "Scout/Concepts/ValueField"
(→Description) |
(→Added NumberField and DecimalField to fields not to be used in forms) |
||
| Line 6: | Line 6: | ||
* extends: {{ScoutJavadoc|AbstractValueField<T>|C}} | * extends: {{ScoutJavadoc|AbstractValueField<T>|C}} | ||
| − | == Description == | + | == Description == |
| − | + | ||
| − | + | Value fields allow the user to enter some values in the form. Scout provides different implementation of the value fields, in order to add properties and event specific to the type ({{ScoutProp|MinValue}} on {{ScoutLink|Concepts|IntegerField|IntegerField}}, or {{ScoutProp|InputMasked}} for {{ScoutLink|Concepts|IntegerField|StringField}}) | |
| − | === Type of Value Fields === | + | {{important|Do not use this field in your forms|This class mutualizes the all the common logic for all values fields (validations...) but there is no renderer for this field. You should consider using one of the child classes, depending on the type of the value you want to display. Other such fields that provide common functionality to extensions but have no renderer are NumberField and DecimalFieldand; they shouldn't be used in your forms, either.}} |
| − | * {{ScoutLink|Concepts|StringField|String Field}} | + | |
| − | * {{ScoutLink|Concepts|IntegerField|Integer Field}} | + | === Type of Value Fields === |
| − | * {{ScoutLink|Concepts|LongField|Long Field}} | + | |
| − | * {{ScoutLink|Concepts|DoubleField|Double Field}} | + | *{{ScoutLink|Concepts|StringField|String Field}} |
| − | * {{ScoutLink|Concepts|DateField|Date Field}} | + | *{{ScoutLink|Concepts|IntegerField|Integer Field}} |
| − | * {{ScoutLink|Concepts|TimeField|Time Field}} | + | *{{ScoutLink|Concepts|LongField|Long Field}} |
| − | * {{ScoutLink|Concepts|CheckboxField|Boolean Field}} also called {{ScoutLink|Concepts|CheckboxField|Checkbox Field}} | + | *{{ScoutLink|Concepts|DoubleField|Double Field}} |
| − | * {{ScoutLink|Concepts|SmartField|Smart Field <T>}} | + | *{{ScoutLink|Concepts|DateField|Date Field}} |
| − | * {{ScoutLink|Concepts|ListBox|List Box <T[]>}} | + | *{{ScoutLink|Concepts|TimeField|Time Field}} |
| − | * {{ScoutLink|Concepts|TreeBox|Tree Box <T[]>}} | + | *{{ScoutLink|Concepts|CheckboxField|Boolean Field}} also called {{ScoutLink|Concepts|CheckboxField|Checkbox Field}} |
| − | * {{ScoutLink|Concepts|RadioButtonGroup|Radio Button Group <T>}} | + | *{{ScoutLink|Concepts|SmartField|Smart Field <T>}} |
| + | *{{ScoutLink|Concepts|ListBox|List Box <T[]>}} | ||
| + | *{{ScoutLink|Concepts|TreeBox|Tree Box <T[]>}} | ||
| + | *{{ScoutLink|Concepts|RadioButtonGroup|Radio Button Group <T>}} | ||
== Properties == | == Properties == | ||
Revision as of 05:25, 22 January 2013
| Scout |
| Wiki Home |
| Website |
| Download • Git |
| Community |
| Forums • Blog • Twitter • G+ |
| Bugzilla |
| Bugzilla |
Specific type of Fields that contains a value. Depending on the type of value, one of the child class needs to be considered.
- implements:
IValueField<T> - extends:
AbstractValueField<T>
Contents
Description
Value fields allow the user to enter some values in the form. Scout provides different implementation of the value fields, in order to add properties and event specific to the type (MinValue on IntegerField, or InputMasked for StringField)
Do not use this field in your forms
This class mutualizes the all the common logic for all values fields (validations...) but there is no renderer for this field. You should consider using one of the child classes, depending on the type of the value you want to display. Other such fields that provide common functionality to extensions but have no renderer are NumberField and DecimalFieldand; they shouldn't be used in your forms, either.
This class mutualizes the all the common logic for all values fields (validations...) but there is no renderer for this field. You should consider using one of the child classes, depending on the type of the value you want to display. Other such fields that provide common functionality to extensions but have no renderer are NumberField and DecimalFieldand; they shouldn't be used in your forms, either.
Type of Value Fields
- String Field
- Integer Field
- Long Field
- Double Field
- Date Field
- Time Field
- Boolean Field also called Checkbox Field
- Smart Field <T>
- List Box <T[]>
- Tree Box <T[]>
- Radio Button Group <T>
Properties
Defined with getConfiguredXxxxxx() methods.
TODO
Add a description of important properties. The idea is not to recreate the JavaDoc of the getConfiguredXxxxxx() methods but to provide explanations, best practice, example... Group the properties by domain.
Add a description of important properties. The idea is not to recreate the JavaDoc of the getConfiguredXxxxxx() methods but to provide explanations, best practice, example... Group the properties by domain.
Events
Defined with execXxxxxx() methods.
See also the Field page for the events that all fields have in common.
Input validation
- ParseValue: event to define how the text (String) typed in the UI is converted in a value.
- ValidateValue: event to add business logic to define if the value is valid.
- FormatValue: event to define how the value is displayed in the field (as String). This function need to be "compatible" with ParseValue
- ChangedValue: At this point the validValue is accessible with getValue().
Other events
- IsSaveNeeded
- MarkSaved
- IsEmpty