W3C home > Mailing lists > Public > www-forms@w3.org > April 2002

A few XForms Questions...

From: Dan G. Switzer, II <dswitzer@oar.net>
Date: Tue, 2 Apr 2002 10:10:40 -0500
To: <www-forms@w3.org>
Message-ID: <006201c1da58$8d401950$d66112c7@dan>
I had a few general questions that I haven't seen directly answered on
the XForms site. I've been developing an open source JavaScript API
(called qForms) for about 18 months. While XForms & qForms are not
directly related, there are similarities in that we're both trying to
provide a consistent method for handling/creating forms.

As flexible as XForms is, there are a few things that seems to be absent
from the XForms spec, which seem to be some of the most used features of
qForms:

1) The ability to treat a select box as a "container." qForms allows you
to bind select boxes together so that items can be moved from one select
box to another. Also, items marked as a "container" post all the options
in the select box back to the server.

2) The ability to create n-related select boxes. This is the ability to
relating select boxes together so that the value in one select box
changes depending open a parent select box.

Are this features there and I'm just missing them, or are they outside
the scope of what XForms is targeting to do? I'm really interested in
following how XForms progresses, because I see a lot of interoperability
between the two--especially since the qForms engine will work in NS3+.

Anyway, looking forward to what's to come.

-Dan

qForms JavaScript API:
http://www.pengoworks.com/qforms/
Received on Tuesday, 2 April 2002 10:09:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:21:51 GMT