Re: widgets plan proposal

Andrew Kohlsmith <[email protected]> writes:
> What direction is xwt heading toward -- will there ALWAYS be an
> xwt.theme() (I think there was talk of moving this to an
> xwt.overlay() call instead) statement?

I see it as being like X11 and window managers.  You can run XWT
without a theme installed, but you wouldn't *want* to do it.

> The second question ties in with the previous point -- at least in what Rod 
> and Charlie have done now, what is proposed to be impl doesn't actually have 
> a theme -- it's the bare minimum to achieve the desired behaviours that 99% 
> of the themes will use anyway.  The button for example, has the boxes and the 
> code to handle hovers, presses and whatnot, but does not have the boxes which 
> have the dotted border of monopoly focused widgets, or the bevel that goes 
> away when pressed.

That sounds like almost exactly what I'm calling for.  Excellent.

> Do you have any issues with me pointing my cron job over to
> cvs.xwt.org to do cvs exports to provide daily CVS snapshots?

Fine with me.

> I would rather have the same strict policy you have set out for the engine.  
> Once the widget tree is declared happy, any changes to that widget tree 
> should be cleared by consensus before commit.

Interesting.  How about if I fork of stable branches periodically, and
you can only commit to those branches with consensus approval?

> I'll take a look at it.  What software are you using to generate thse reports?

Custom perl scripts.

  - a



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