W3C home > Mailing lists > Public > public-forms@w3.org > December 2007

Re: Proposal for submission in XForms 1.2

From: Erik Bruchez <ebruchez@orbeon.com>
Date: Mon, 17 Dec 2007 16:13:23 -0800
Message-Id: <0C7FC6D8-9E02-4BFE-B370-D53DD2333F18@orbeon.com>
To: Forms WG <public-forms@w3.org>


This sounds like an appealing proposal to me.

I had a different take on it at some point, by suggesting to allow  
using xforms:submission as an action. The main use case is within a  
sequence of actions, where you do get an indirection the way things  
are done today. If you use your submission only once, why do you have  
to define it far away from where you use it?

So in either case, it seems that the idea is to better group related  
code and make it easier to read and write.


On Dec 17, 2007, at 4:00 PM, Ulrich Nicolas Lissť wrote:

> Hello all,
> one of the future features for XForms 1.2 is a standalone submission
> element to enable model being optional.
> However, I'd rather propose to allow submission to be a child  
> element of
> the submit element. The submit/@submission attribute would become
> optional in this case. The default action for DOMActivate would be to
> dispatch xforms-submit to its submission child element.
> I think this would be helpful for ease of authoring since it removes  
> one
> level of indirection. Also, all possible event handlers for
> xforms-submit-* would be located near to its originating submit  
> element.
> Furthermore, with instance and binds already being optional and
> submission being encapsulated in submit, we have would only have UI
> elements as top-level elements once model is optional.
> What do you think?
> Regards,
> Uli.
> -- 
> Ulrich Nicolas Lissť

Orbeon Forms - Web Forms for the Enterprise Done the Right Way
Received on Tuesday, 18 December 2007 00:13:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:48:27 UTC