W3C home > Mailing lists > Public > www-forms@w3.org > June 2000

Re: XForms not enough

From: John Ky <hand@syd.speednet.com.au>
Date: Sun, 11 Jun 2000 01:42:35 +1000
Message-ID: <000801bfd2f2$80329360$9800a8c0@hoggy>
To: <www-forms@w3.org>
> Anyway, as I have said, HTML Components is very important but first there
> should be a set of built-in components that every browser ships with.
Look
> at XUL for ideas of what is most important.

But AFAIK, XUL itself is largely made up of XBL + CSS + some primitive
set of controls.

> The problem with applying the title "forms" to a UI XML language is that
UIs
> are not really limited to the forms paradigm.  So, to me it would make
sense
> for the XForms spec to not require or specify any particular type of user
> interface controls. They should leave the specific UI stuff to a separate
> set of XHTML modules.

Be careful there and don't become to general and lose touch with the
original
purpose of XForms.  I would like to see something more general than "forms",
but we need to start from somewhere concrete first.  A good starting point
would be to have a possible solution to the current XForms requirement for
everyone to look at and then comment on what it can and can't do.

Also, as XForms is suppose to cover more than XHTML, I don't see
much of a problem in that regard.

I hope browsers that implement the XForms XHTML module don't have
it hard coded.  The flexibility of being able to create alternative ways of
visualising the content of a form (down to the behaviour level) would be
a very powerful feature.

-John
Received on Saturday, 10 June 2000 11:38:44 GMT

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