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

Re: Why doesnt Xforms allow submission responses to target specified model.instance.node replacement?

From: Jason <jeacott@hardlight.com.au>
Date: Sat, 24 Jun 2006 12:01:01 +0930
Message-ID: <449CA3E5.3020005@hardlight.com.au>
To: mark.birbeck@x-port.net
CC: www-forms <www-forms@w3.org>

ah - cool,
	thanks Mark, thats an encouraging step forward. One day I'll be lucky 
enough to get the chance to use Xforms 1.0+ ;-)
The next thing that I'd really like to see is a good dev environment for 
xforms. Building them by hand and getting them to work seems to take me 
an age - especially when I havent done it for a while. I've tried the 
eclipse plugin but its still not quite what I'm after. for bread & 
butter forms I tend to just use my little formbuilder form these days, 
but for anything special it takes me a while. The fact that I cant 
"compile" or otherwise verify that at least all my refs resolve before I 
start testing is something that wastes a lot of time I think.

Thanks again
Jason.





Mark Birbeck wrote:
> Hi Jason,
> 
> This was indeed a glaring omission in XForms 1.0, but it was to a
> large extent rectified in an erratum...there is now an attribute on
> xf:submission to identify the instance to replace with the results, so
> preserving your original request.
> 
> This still doesn't allow you to target a particular node to be
> replaced, but when combined with the new @origin attribute on
> xf:insert (in XForms 1.1) you can easily move things around in the
> xforms-submit-done event handler.
> 
> The @instance attribute on xf:submission is described here:
> 
>  <http://skimstone.x-port.net/node/99>
> 
> The new xf:insert features are described here:
> 
>  <http://skimstone.x-port.net/node/339>
> 
> Regards,
> 
> Mark
> 
> 
> On 23/06/06, Jason <jeacott@hardlight.com.au> wrote:
>>
>> Hi all,
>>         I keep running into this and wishing that Xforms supported it.
>> Is there any reason why as part of the xforms submission element there
>> isn't or couldn't be the option for something like:
>> <xf:submission id="dostuff" action="someaction" method="post"
>> replace="instance('somethingotherelse')/response"
>> ref="instance('myxmlservicesblock')//getsomething" />
>>
>> this bit:
>>   replace="instance('somethingotherelse')/response"
>>
>> is what I'm interested in.
>> would be mega handy for returning error messages and other info a user
>> might be interested in without having to be sure to collect the the
>> entire submitted instance + any extra stuff for every submission that
>> might have extra info attached.
>> It would also make using soap etc much easier because a bunch of
>> preconfigured soap 'templates' could then be easilly used and reused.
>> the only way I know to do this currently is to submit an instance
>> containing a soap request with replace="instance" then do something with
>> the result, at which point you cant resubmit if you want to because your
>> request is gone.(or can you? is there a way?)
>>
>> maybe this would work - havent tried it and it sounds horrible.
>> maybe when you want to do the submission again you could delete the
>> instance root and then create a new one so that your original "default"
>> xml gets rebuilt? would that work?
>>
>> just a question - it doesn't seem to me that this kind of addition would
>> violate the xforms ethos at all.
>>
>> any thoughts?
>> Regards
>> Jason
>>
>>
>>
>>
>>
>>
>>
>>
> 
> 
Received on Saturday, 24 June 2006 02:31:14 GMT

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