> > However, you are welcome to have an empty caption on a CheckBox and > place it wherever you want, or even roll your own CompoundButton that > has no caption. > Well my point is that there doesn't seem to be a consistent recommendation on where stuff should be. Sometimes its on the left, sometimes its on the right.
The suggestion to use empty labels and then put another text label on the left of a checkbox makes experience different from CheckBox. Checkbox will also toggle if you hit the text, not only the box. I know that it is possible to override this but whats the point of having a UI framework in that case? IMHO it is here to aid and (partially) enforce a consistent user experience. Right now if someone asks me where the box in a checkbox is then you typically have to answer, "well it depends on ....". This is weird. > So long as it is obvious to your users what the checkbox corresponds > to, its precise placement does not matter a lot. > IMHO it matters from a consistent UE experience. Android design is all about tightening the reins and making the UE more consistent. Funny enough even in their examples it is sometimes left and some times right. The rule with "in a list its right, otherwise right" is also a bit dodgy. For example the google music context menu has a single checkbox option on the right, even if you could argue whether this is a list or not. Also if I have a dialog with a bunch of form elements (username, password, remember checkbox) then what should it be there? You can argue that in total it looks similar like a list, but then by default its still on the right. I just don't get it. > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
