widgets plan proposal

After catching up on the mailing list, including David's recent post
about his role as widget czar, here's my proposal for moving forward
with the widgets repo.

I'd appreciate it if all the parties who are substantially involved in
this could indicate a boolean agree/disagree on each section and then
provide comments.


______________________________________________________________________________
1. Widget naming structure

   xwt.widgets -- each template is simply an empty template which
                  preapplies the appropriate xwt.impl template and any
                  relevant "adjectives" (focusable, etc).  A <doc/>
                  element should specify the contract between
                  implementations of that widget and its users.  You
                  shouldn't overlay other templates on top of
                  xwt.widgets.

   xwt.impl    -- individual templates in xwt.widgets pre/post apply
                  these; new themes should overlay xwt.impl with the
                  theme-specific templates.  In general, xwt.impl
                  templates should not apply "adjective" templates.

                  The "default" implementation (ie the actual xwt.impl
                  templates, not the stuff overlaid on top of it)
                  should be super-simple and hideously ugly (sorta
                  like the Xaw widgets).

   xwt.lib     -- templates containing only code; intended to be
                  preapplied/postapplied to other templates in order
                  to import commonly used functionality.  You should
                  not overlay other templates on top of xwt.lib.


______________________________________________________________________________
2. Getting stuff moved to cvs.xwt.org

Import the mixdown cvs tree as the 'audit' branch on cvs.xwt.org.
Andrew and Charles are given sole authority over this branch; they may
delegate it as they see fit.  I will not meddle with this branch.
Just to be 100% clear, you DO NOT have to ask me for commit approval
unless you're patching the engine.


______________________________________________________________________________
3. Merging, implementing the new namespace

David has offered to take charge of merging the changes from the audit
branch onto HEAD, renaming the widgets as needed to comply with the
naming structure we end up settling on.

Andrew/Charles, at some point David will ask you for a 48-hour "cease
development" synchronization point (you should negotiate when this
will happen).  Before that point, check in all your work-in-progress,
and then cease development for 48 hours.  During this time, David will
complete the merge over to the HEAD branch.


______________________________________________________________________________
4. The aftermath

Once that is completed, David steps down as widget czar, and the
position is eliminated.

The people remaining in the commit_widgets group (andrew, charlie,
david, megacz [later: rod?]) divide responsibility for the widgets by
consensus.

Architectural changes (ie xwt.widgets.*) should be agreed upon by
consensus before checkin; anything else is commit-at-will if you've
taken responsibility for the widget in question.

I recommend that you all watch the [email protected] mailing list -- it's a
neat way to keep an eye on what other people are doing.


--

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