Re: FINAL CALL

> Charlie, you need to post specific examples of these mysterious
> "problems" instead of just alluding to them.

I gave examples, repeatedly.  Stuff needs to be split up, it really does,
into common layout/keybindings code and theme independent code.  However,
it's... perverse to have xwt.lib.layout.widget preapply xwt.lib, isn't it?
:/

xwt.theme -> I understand this one a little better now, you want people to
import xwt.widget, right, then xwt.widget preapplies xwt.theme which is
overlayed by overlay() to some.theme.dir and some.theme.dir preapplies stuff
from xwt.lib - right?  Which I see works fine.

However, does this mean xwt.overlay() is just going to be xwt.theme()
renamed?  It's doing exactly the same job.  All you are doing is moving what
is being themed, around.

I'd rather have the 'theme dependent' code go into xwt.theme, and have
xwt.standard as the 'overlay' dir, and then have that as a actual theme.

xwt.widget
|- preapply xwt.standard
            |- preapply xwt.theme
            |           |- preapply xwt.lib
            |- preapply xwt.lib

This would save having an awkward subdir in xwt.lib.  Maybe xwt.lib ->
xwt.theme.lib?
_______________________________________________
http://lists.xwt.org/listinfo/dev