+1 - I think properly modeling the field using the required-field
attribute makes perfect sense. I would think our html form renderer
implementation should probably just apply a class "required" at render
time and the visual should be handled by css.
On Apr 23, 2010, at 2:35 PM, Bilgin Ibryam wrote:
Here is what I propose:
Remove all the ${uiLabelMap.CommonRequired} tooltips from form
definitions. The tooltip should be used to provide other information
as it is for not required fields (the purpose of the field, the
format)
Remove all the widget-style="required" from form definitions.
If a field is required, (on form widget) set only its attribute
required-field="true". In cases when the form is based on service
definition (auto-fields-service) it is not neccessary to set this
attribute. Then no need to add tooltip="$
{uiLabelMap.CommonRequired} or widget-style="required" attibutes on
the form definition. The renderer should decide how to indicate the
required field.
Change form renderer, so if a field is required it is indicated by
asterix plus required style ( same as widget-style="required")
