Re: Last call on the selectable naming issue

Adam Megacz <[email protected]> 28 Oct 2003 13:28:42 -0800
Newsgroups gmane.comp.java.xwt.widgets
Organization XWT
Message-ID <[email protected]>
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.

  - a

Charles Goodwin <[email protected]> writes:
> Ok, the choice is simple; one of the following 4.
> 
> ["can-be-selected-widget" and "part-of-selection-group"]
> 
> In no particular order:
> 1.  selectable and electable
> 2.  selectable and muxselectable
> 3.  selectable and selectionable
> 4.  markable and selectable
> 
> Markable is a late entrant in that I've only recently really considered 
> it.  Pros: short and sensible.  Cons: selected=bool not marked=bool.
> 
> Please put in your prefered order.  I'll assign points according to 
> position (1=5pts, 2=3pts, 3=2pts, 4=1pt) and add up the totals.
> 
> Winner takes all.  Also, please add a yes/no on vote weighting where 
> 'yes' means mine (as main widget dev) and Adam's (as XWT deity) votes 
> count twice.
> 
> My order: 4, 1, 3, 2
> On weighting: yes
> 
> Please tell others to vote, although unrecognised names don't get to 
> vote (ie if you haven't contributed / been around) so you can't sabotage it.
> 
> - Charlie
> 
> 
> _______________________________________________
> widgets mailing list
> [email protected]
> http://lists.xwt.org/listinfo/widgets
> 

-- 
"Education is not filling a bucket but lighting a fire." -- WB Yeats