Re: widgets plan proposal

> Charles Goodwin <[email protected]> writes:
> > I also liked the way Rod and I work on a system where the 'behaviour'
xwts,
> > the non-widgets, are split from the actual widgets.  It makes it easier
to
> > browse and find what you want, quickly.
> 
> You have a really good point here.  Behaviors logically belong in
> xwt.lib, yet they should be themeable as well!
> 
> How about we have xwt.lib.<behavior> postapply xwt.theme.<behavior>?
> So xwt.lib.focusable postapplies xwt.theme.focusable, which lets
> themes implement theme-specific focusing behaviors.

That still doesn't separate the behavioural widgets from the actual widgets.
And some of the actual widgets, actually most of the complex ones, have 2
versions, 1 for .lib and 1 for .theme.

> Also, I want to add an ignore-if-not-found attribute to the pre/post
> apply element.  This way we don't have to have a jillion empty
> templates in xwt.theme.

Noooooooooo this is bad.  It worked like this before... no error if you
mispelt a preapply.  It was a nightmare to find.  This is a case of a little
less laziness makes for a much easier time... let's just not be lazy and
only pre/post apply where needed. :)
_______________________________________________
http://lists.xwt.org/listinfo/dev