Re: plan for xwt.standard

David Crawshaw <[email protected]> writes:
> A simple app developer wants the simplist possible interface... The
> buttons should just be focusable. No extra thought.

> Others need access to fully functional widgets without the adjectives 
> applied.

Argh, good point.  Could you document this rationale (and the layout
of xwt.standard) in the widgets README for posterity?

> xwt.standard
> xwt.standard.impl
> xwt.lib

Okay, I dig it now.  This architecture is both sound and minimalist.

Since this appears to be a fairly major upheaval, could we take this
opportunity to pick some better names?  I'm starting to regret picking
the word "standard" -- it doesn't tell you much and it requires a lot
of keystrokes.

Howabout:

  xwt.standard      -> xwt.widget
  xwt.standard.impl -> xwt.theme
  xwt.lib           -> xwt.lib

The second one looks confusing at first, but once xwt.theme() becomes
xwt.overlay() [or xwt.mount()], that will go away.

> As evidence against control variables, I submit:
> http://java.sun.com/j2se/1.4.1/docs/api/javax/swing/JTextPane.html

Yes, javax.swing will be a fertile source of examples of how *NOT* to
design a widget set ;)

  - a

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