Re: Last call on the selectable naming issue

Adam Megacz wrote:
> Hey, what if we merge selectable and {electable|muxselectable|etc} and
> provide an attribute 'maxselectable' that defaults to 1?
> 
> Then a 'selectable' is just a selectable in a group by itself, and an
> 'electable' is just a selectable that's grouped with other
> selectables?
> 
> This generalizes nicely to the case where you have a list of items of
> which a fixed number (say, only three) can be selected.

There was a reason we didn't do this; that 'check' would never be an 
electable IIRC.

However, you just made me think about it a little more.  One of the 
original issues with a multi-selection group is that when you reach the 
maximum do you a) prevent more selection until deselection has occurred 
or b) do you do rolling selection, deselecting as needed?

To illustrate the example, think of a group of radios.  Selecting one 
unselects the selected; that's rolling selection.  However, if it were a 
group of checks then, upon having reach the maximum selected, you'd have 
to deselect before selecting more.

You probably noticed a direct contradiction or my/our original 
assertion; checks are optionally electable.

Okay, unless anybody objects, I'll roll this into selectable.  Damn, 
that ruins the fun of the vote.

- Charlie