Closed alexlockhart7 closed 8 years ago
Two questions / update requests and then I can merge this in:
1) Is there a reason we need to add value as an attribute to the Checkbox annotation? Can the one tied to DialogField not be used for this purpose? 2) While I agree that it would be rarely used in the Touch UI it would be nice to keep the checked option. Can we change the annotation such that it takes a list of booleans? That way we can actually differentiate between the user not setting the attribute and setting it to false. An empty list should cause the property not to be added to the dialog output. A list with one or more elements should cause the property to be added to the dialog output and its value should be the value of the first element in the list. If the list contains more than one element a warning should be logged indicating we only care about the first element.
@pmichelotti Both of your suggestions have been added.
Changed the TouchUI CheckBox annotation in two ways:
The usage of the different attributes in the touch ui checkbox xml is a bit awkward and unexpected. So if you feel that I might be wrong about this, read the documentation carefully. However I think that we want to set the "value" attribute instead of the "checked" attribute, which is what this pull request does.
Relevant documentation:
Granite Checkbox Documentation CRX path to checkbox JSP: /libs/granite/ui/components/foundation/form/checkbox/checkbox.jsp