Re: Organising the xwt namespace

> - The name. For some reason, 'skill' is really growing on me. I think 
> it's the one-syllable nature and the fact it isn't used in any other 
> libraries I can think of. Still, it's not that important. I just think 
> we should do better than 'common', which is a little too general for my 
> liking (but definitely better than 'shared').

widget is 2 syllables. :)

> - Do we also need xwt.lib.<behavior>? xwt.lib is going to have a lot 
> less things in it then xwt.theme, and I was hoping we could just drop 
> them in there together. Still, this is not very important, and perhaps 
> we should put it off until it actually comes time to do the cvs 
> transition.

May as well decide now.  I would say that if you have an
xwt.theme.<behaviour> namespace then for consistency you should have an
xwt.lib.<behaviour> namespace.
_______________________________________________
http://lists.xwt.org/listinfo/dev