Closed GoogleCodeExporter closed 9 years ago
Can you give me a quick scenario where this would be useful? The grid to me is
more of a list of data unrelated to eachother other than their parent.
Original comment by Seancla...@gmail.com
on 14 Mar 2011 at 4:37
Hey, this email address was down for a bit, so sorry for the late reply. Grats
on 1.4 btw, I'm going to try it out shortly.
Re: Multi Checkbox/Radio Support ---> Well the specific utility of using a
group of checkboxes or radio buttons is usability.
When you select items from a drop down menu, it's a click, hold,
mouseover/drag, select operation for one entry.
For multi-select menus where you are attempting to create a one-to-many
scenario, you have to know to hold down a CTRL- or SHIFT- modifier. Even
though it's a relatively common usage convention, it's not intuitive or an
efficient use of clicks.
For short lists, a well organized set of radio buttons or drop downs present
the information in a more accessible manner. This obviously depends on the
information and styling, but ultimately, it's merely a statement that says,
DROP DOWN select is not the only way to present a lookup list of choices. A
grouped set of checkboxes or radio buttons accomplishes that goal as well, with
less clicking, and less eyeball strain (because the choices are all visible at
once).
Your mileage will vary of course. A list of 1000 choices is not a good
candidate for either selection mode without some form of categorization.
Original comment by vep....@gmail.com
on 21 Mar 2011 at 7:50
I see what you mean, you mean 1 field has many options not that 2 rows have
related checkbox data.
Sooo the solution to that is subgrids. You don't want to have 1 to many
relationships in each row. But sub grids will allow that, and much more
flexibility. You can have multiple subgrids per row. This is a grid 2.0
feature, and is requested by some corporate clients, but that will solve both
of these situations.
Original comment by Seancla...@gmail.com
on 31 Mar 2011 at 2:54
Original comment by Seancla...@gmail.com
on 4 Apr 2011 at 5:28
Original issue reported on code.google.com by
vep....@gmail.com
on 11 Mar 2011 at 6:49