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

AW: XForms-processor as applet

From: Josef Dietl <josef@mozquito.com>
Date: Wed, 14 Jun 2000 10:51:20 +0200
To: <schulze@dresden-informatik.de>, <www-forms@w3.org>

I agree on the problems, and we already have an implementation path fitting
all your requirements plus it doesn't require the installation of a
plug-in. (If you have to install a plug-in, you may as well ask people to
upgrade their browsers. We want to enable the existing browser population
right away.) While XForms isn't available yet, we are using our own Forms
Markup Language which is based on XHTML Modularization.

Our solution is: we take documents (today in XHTML-FML, as soon as feasible
XForms) and convert them into HTML4+JavaScript. This conversion can happen
on the server or in the authoring tool.

This approach solves the support-by-browser-vendors problem and enables the
exisiting installed browser base to use enhanced forms right away. The
approach to gradually load database tables is also in the works, even
though it's not avilable yet.

Stack Overflow - We Help Increase Your Productivity With XHTML
Visit http://www.mozquito.org

> -----Ursprüngliche Nachricht-----
> Von: www-forms-request@w3.org [mailto:www-forms-request@w3.org]Im
> Auftrag von schulze@dresden-informatik.de
> Gesendet: Dienstag, 13. Juni 2000 16:42
> An: www-forms@w3.org
> Betreff: XForms-processor as applet
> Unfortunatly this discussion becomes a bit diverse, so here's my
> opinion:
> I think one drawback of XForms could be missing / late / inaccurate
> support by the browser vendors. So did someone ever think about
> implementing XForms as an applet that runs in every HTML4-browser? This
> applet could retrieve all necessary data (dtd or xml schema + form-data
> + xforms-definition) via http and then render (possibly browserspecific)
> html4 using xsl.
> I've worked out some ideas about this approach because I also believe
> that the request-response principle does not suite well for editing
> forms. For instance, if you want to implement flexible editing of a
> database table, the underlying data should be gradually transported over
> the web: first the browser downloads all initially visible data (plus a
> few extra) and requests the remaining as the user scrolls down. All as
> XML, of course.
> => the model- and instance data should be allowed to be declared by url
> => large amounts of instance data should be retrieved gradually
> => the html4 should be generated in respect of the xml-schema or dtd
> => html4-generation should be customizable via different xsl-stylesheets
Received on Wednesday, 14 June 2000 04:48:29 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:03 UTC