Re: widgets plan proposal

On Wednesday, April 2, 2003, at 12:10  PM, Adam Megacz wrote:
> Can the template xwt.theme.button also contain a bare-bones, ugly
> implementation of a button?

Well, I'm willing to go either way on this, however I do like the idea 
of a bare implementation being in xwt.theme.

My two reasons being:
- Documentation makes a lot more sense when there is the cleanest 
possible implementation sitting next to it. It's all well and good to 
say "preapply xwt.lib.button, jump through hoop a while twisting hoop b 
90 degrees right", but code can sometimes make things clearer than 
english.

- One day I hope each theme will be in its own xwar, and a standard 
xwar will be maintained on xwt.org, and the builtin control panel will 
decide all the themeing. In such a modular environment, it would 
simplify things (IMO) to have the base widget module functional without 
any of the option org.xwt.* packages.

Basically, I'd like to see xwt.* stand on its own feet in debug/ultra 
light (hiptop?) style situations. As such, I don't think we need to 
deliberately make a default theme ugly, we just shouldn't clog it up 
with jpgs.

Of course, with embeddable svg coming, you could make a default theme 
look quite good without any extra image files.


> Otherwise I totally agree.
>     http://wiki.xwt.org/Wiki.jsp?page=PNGWA

Cool.

d


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