Re: typeof

> Not sure if we need a general attribute 'type' however for the 
> different widget as Charlie is suggesting. Perhaps we should have a 
> rule however that all adjective templates (-able) have a boolean 
> attribute with the same name as the template, and set it to true when 
> active. This is almost the case already.

There's not enough context using just the 'able' part of things.

The best example are selection_mux items like radiobutton.  If you want to
handle all of that automatically then you need to know that you're receiving
radiobuttons, not clickables, not focusables, and not even 'mutually
exclusive selectables'.

A radiobutton only wants to be grouped with other radiobuttons.

Perhaps, though, this is wrong... perhaps we should go the -able route...
it'd just mean you'd have to clearly separate things that might conflict:

<group>
    <other_smux />
    <group>
        <rb />
        <rb />
        <rb />
    </group>
    <other_smux />
    <other_smux />
</group>

Is that really a bad thing?
_______________________________________________
http://lists.xwt.org/listinfo/dev