Re: File Structure

> I got a little sick of our old names, which was a bit of a mishmash of 
> other widget libraries. For some reason, we have a checkBox, but we 
> also have a radioButton. I figured:
> - everything is a box, so drop the *box suffixes
> - check and radio are not really buttons
> - what does edit edit? it's really a textbox, which can be edited. then 
> we drop box -> a la text.

I kinda agree with you here.  But (isn't there always a but?) you also have
to adhere to 'standard naming' sometimes.

However, personally, I like the shorter to-the-point names that you suggest.
I do think edit should stay as edit though, and text should be a factoring
of edit that makes it somewhat more useful... maybe... unless that's
completely unecessary.  I'm not sure though.  I've not gotten into edit all
that much - that's more your/Andrew's/Rod's speciality.

> The rich text editor I'm working on would fit in as:
> 
> xwt.html.* - start from scratch rendering library
> xwt.theme.richtext.* - themeable selection model and editor build on 
> top of (preapplies) xwt.html
> xwt.widget.richtext - simple rich text editor, with a menu child in it 
> that can be put somewhere useful by the application (buttons for Bold, 
> Italics, Underline, Font, Color, etc).

I'd rather see richtext go under either xwt.util.richtext or xwt.richtext,
it's complex enough to warrant it's own namespace, for sure, and it's not
really a core widget.  Or is it?

> I really didn't want to start xwt.html from scratch, but I have a week 
> coming up in which I'll put the preliminary support development, and 
> hopefully I can justify my actions.

/me drools in anticipation.  If you can work on html some of that same magic
you used on edit, it'll be damn fine.  Deee-yamm faiii-n. :)
_______________________________________________
http://lists.xwt.org/listinfo/dev