Re: widgets plan proposal

Andrew Kohlsmith <[email protected]> writes:
> > I don't actually understand this. xwt.lib is code that is theme
> > independent, right? In which case, behaviors still belong in xwt.theme.

Yeah, good point.

> A lot of themes change the form (highlight, sparkle, whatever) when
> hovered.  These are all common behaviours -- why put the code that
> does foo to a button when it's hovered or clicked or disabled or
> whatever in each theme?

For something like hover, you're right -- it will be common to all
themes.  However, something like focusable could work differently in
different themes.  A while back we had some discussions about a cool
new dialog focus system that popped up a tooltip on every focusable
when you hold down alt; each tooltip contains the alt-X key you have
to hit to focus that widget.  So it would be useful for focusable to
be themeable.

I guess that in general, adjective templates (like focusable) go in
xwt.theme unless you're 100% certain that they will be the same in
every theme (like hover, clickable, etc).  Even in the former case,
common functionality can be placed in xwt.lib.

> ALL widgets across ALL themes have _action which gets called when the user 
> activates the widget and it is not disabled.

Does "activate" mean "chosen", "focused", or "selected"?  These three
words do not mean the same thing.

For example, in a MacOS finder window, an icon can be selected (single
click -- hilighted), chosen (double click -- opened) or focused
(editing the icon's name/text).

You are right, however, that there was a TON of inconsistency in the
widget library.  Thanks for ironing this stuff out.

  - a

_______________________________________________
http://lists.xwt.org/listinfo/dev