OxJS: All form elements should have "value" #209

New issue

Closed

opened 2011-11-27 02:38:46 +00:00 by rlx · 1 comment

rlx commented

2011-11-27 02:38:46 +00:00

Owner

In order to make forms more consistent, "value" should be generalized for form elements. It's not 100% clear if this should always be self.options.value, or if {..., selected: true} or {..., checked: true} makes more sense for Selects or , in which case we'd need a that.value() getter/setter. Forms should have "value" too (rather than "values"), and should combine their Form's values as "value" as well. It may even be interesting for Lists to have a value (the array of selected ids), so they could be used as multi-selects.

In order to make forms more consistent, "value" should be generalized for form elements. It's not 100% clear if this should always be self.options.value, or if {..., selected: true} or {..., checked: true} makes more sense for Selects or <CheckboxGroups>, in which case we'd need a that.value() getter/setter. Forms should have "value" too (rather than "values"), and <FormPanels> should combine their Form's values as "value" as well. It may even be interesting for Lists to have a value (the array of selected ids), so they could be used as multi-selects.