WD-XForms-20010608

We expect to handle this via xforms modularization;
roughly, 
you should be able to use the model and binding modules from
xforms and bind ui using your favorite vocabulary.
We define a set of UI widgets for XHTML because that is one
of the things we are chartered to do.

>>>>> "Berin" == Berin Loritsch <bloritsch@apache.org> writes:

    Berin> Overall, I want to say that this iteration is
    Berin> even better.  I like the additional UI elements,
    Berin> and the offering of representations of what the
    Berin> UI elements could or should look like.

    Berin> However, it does not address using XForms
    Berin> exclusively.  For instance, the XForms UI *must*
    Berin> be embedded in another type of markup altogether.
    Berin> Embedding the UI in XHTML is nobel, and
    Berin> necessary--but for XForms to be mature, it also
    Berin> needs to be able to stand alone.  I would like to
    Berin> be able to use a layout manager to handle
    Berin> placement of the UI elements on the screen--and
    Berin> not bother with XHTML altogether for some
    Berin> instances.  An example would be using XForms UI
    Berin> to create a Java Swing dialog box according to
    Berin> Sun's Layout guidelines.  Clearly, XHTML does not
    Berin> apply in this situation.

    Berin> I don't necessarily want to see horizontal rules
    Berin> or other things like that in the spec, just
    Berin> simple groupings of UI elements that is separate
    Berin> and distinct from XHTML.

-- 
Best Regards,
--raman
------------------------------------------------------------

IBM Research: Human Language Technologies
Phone:        1 (408) 927 2608
Fax:        1 (408) 927 3012
Email:        tvraman@us.ibm.com
WWW:      http://www.cs.cornell.edu/home/raman
PGP:          http://emacspeak.sf.net/raman.asc
Snail:        IBM Almaden Research Center,
              650 Harry Road
              San Jose 95120

Received on Monday, 11 June 2001 13:40:33 UTC