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

Re: New To Do Lists example online

From: Erik Bruchez <erik@bruchez.org>
Date: Thu, 03 Nov 2005 00:22:47 +0100
Message-ID: <43694A47.4020601@bruchez.org>
To: www-forms@w3.org

Jasper,

The OPS XForms engine mostly resides on the server, the client part 
being a fairly simple and lightweight layer (but still daunting to 
write!). This explains why the client performs many Ajax requests to the 
server. This said, there are certainly some roundtrips to the server 
that could be optimized in the future.

-Erik

Jasper Bryant-Greene wrote:
> Your example seems to make a round-trip to the server through
> XMLHTTPRequest for just about everything, including simply selecting an
> item in a list. Why is this? The only noticable effect is a change of
> list item style, which does not require any work on the server's part.
> 
> 
> On Tue, 2005-11-01 at 14:03 +0100, Erik Bruchez wrote:
> 
>>All,
>>
>>I thought I would point to a new example that we developped. It
>>implements a dynamic user interface for To Do lists done 100% with
>>XForms, on top of the open-source-Ajax-enabled OPS XForms engine. Go
>>try it out here (it works with stock Firefox and IE):
>>
>>   http://www.orbeon.com/ops/goto-example/xforms-todo
>>
>>This example illustrates many cool XForms features, such as:
>>
>>   o Nested xforms:repeat
>>
>>   o Use of "relevant" for conditional display of controls
>>
>>   o Typing which allows for automatic formatting of dates
>>
>>   o Use of xforms:submission with instance="replace", here to call a
>>     service able to format an XML document into HTML.
>>
>>   o Use of multiple instances
>>
>>   o Use of xforms:setfocus and xforms:setindex
>>
>>The formatted source code of the page is available here:
>>
>>   http://www.orbeon.com/ops/goto-source/xforms-todo/view.xhtml
>>
>>Constructive feedback is always appreciated!
>>
>>Enjoy,
>>
>>-Erik
>>
>>Note #1: There is no persistence: it's just a UI demo for now.
>>
>>Note #2: We plan for the OPS XForms engine to support Opera and Safari
>>in the future. Like with all Ajax-based software, there is some
>>compatibility work to do to get there, but all modern browsers will be
>>supported at some point. Contrary to most Ajax-based development
>>however, the developers of OPS are taking care of cross-browser
>>compatibility, while you concentrate on writing your application with
>>XForms.
>>
>>Note #3: We are still working on performance (the software is in beta
>>after all).
>>
Received on Wednesday, 2 November 2005 23:22:54 GMT

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