- From: T. V. Raman <raman@users.sf.net>
- Date: Fri, 23 Jun 2006 20:33:46 -0700
- To: jeacott@hardlight.com.au
- Cc: mark.birbeck@x-port.net, www-forms@w3.org
I thought Micah's python tool did some of ref resolution for you? >>>>> "Jason" == Jason <jeacott@hardlight.com.au> writes: Jason> ah - cool, thanks Mark, thats an encouraging step Jason> forward. One day I'll be lucky enough to get the Jason> chance to use Xforms 1.0+ ;-) The next thing that I'd Jason> really like to see is a good dev environment for Jason> xforms. Building them by hand and getting them to work Jason> seems to take me an age - especially when I havent Jason> done it for a while. I've tried the eclipse plugin but Jason> its still not quite what I'm after. for bread & butter Jason> forms I tend to just use my little formbuilder form Jason> these days, but for anything special it takes me a Jason> while. The fact that I cant "compile" or otherwise Jason> verify that at least all my refs resolve before I Jason> start testing is something that wastes a lot of time I Jason> think. Jason> Jason> Thanks again Jason. Jason> Jason> Jason> Jason> Jason> 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 >>> >>> >>> >>> >>> >>> >>> >>> >> -- Best Regards, --raman Email: raman@users.sf.net WWW: http://emacspeak.sf.net/raman/ AIM: emacspeak GTalk: tv.raman.tv@gmail.com PGP: http://emacspeak.sf.net/raman/raman-almaden.asc Google: tv+raman IRC: irc://irc.freenode.net/#emacs
Received on Saturday, 24 June 2006 03:34:10 UTC