W3C home > Mailing lists > Public > www-forms@w3.org > November 2005

Re: AJAX vs. Xforms

From: Jason Eacott <jeacott@hardlight.com.au>
Date: Tue, 8 Nov 2005 11:16:23 +1030
To: Kelly Miller <lightsolphoenix@gmail.com>
Cc: www-forms@w3.org
Message-ID: <43708907.4217.172F3B39@localhost>


> Actually, for the most part, both HTML forms and XForms are pretty 
> useless without some kind of server-side component.  Why go to the 
> trouble of putting together a decent form if you're only going to 
> manipulate it with Javascript?
> 
> I was under the impression that both form libraries were created because 
> it became necessary for the user to input information on a web page for 
> server-side programming to work with.  Personally, the only 100% 
> client-side uses of forms (period) I've ever seen have been insanely 
> basic; generally, the complicated logic is kept on the server-side.

I actually had a use for something like Xforms where a pda was involved in collecting information when 
no server could be available, and then syncronising that data with a server when it got in range. turns 
out there was no realistic means of running an Xform on an ipaq at the time (could barely even find a jvm 
if I wanted one, i was surprised). So whilst this example ultimately requires some serverside tech, it 
was only really for data storage and keeping the forms on the pda up to date. So there really is a need 
to be able to run 'offine', keeping stored data locally until you get a chance to offload it.
The other main problem (besides no xform processor ;-) ) would have been efficient use of the gui space 
because theres not much to work with, and I find Xforms quite tricky to layout and tend to just stick with 
layout UI that already exist.
Received on Tuesday, 8 November 2005 00:46:46 GMT

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