Claudius Spellmann wrote:
Ok just two more questions:
1) The disabled state: Is it enough to just grey out disabled widgets and return any previously selected values or schould the widget-value be null when a widget is disabled.
The disabled state is only from the user point of view: the widget of course holds its value.
2) Should forms also have states so that a whole form can be disabled or hidden.
Being a container, the form will also have a state, which will be inherited by its children with the priority rules I proposed. Using this, you'll be able to disable a whole form at once.
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
