Sorry for my lack of clarity Bryan; I was answering Svante's question: > What I am asking you (with an answer in my mind), what is the great benefit > of XForms, why should we go further with it with OOo? >
I think a good question to be asking. The answer always seemed obvious to me until it seemed folk dismissed XML output as an important factor and carried on with HTTP Forms instead (leaving XForms and Ajax to the 'geeks'). I still think enterprise integration needs a simple way to 'insource' the frontend to enterprise power-users and away from the geeks - to free the skilled developers up for the integration work itself. OOo/SO seem key to this for those who go down the OSS road. 2008/7/9 bryan rasmussen <[EMAIL PROTECTED]>: > On Wed, Jul 9, 2008 at 6:26 PM, Stephen Green > <[EMAIL PROTECTED]> wrote: >> There needs to be a way to make XML the output of a >> form submission. > What do you mean? > I thought that when I submit an XForm the output is XML to the url I > submit it to using the method I use to submit, for example if I PUT to > a http uri it becomes an XML wherever I PUT, dependent of course on > allowability to PUT. > > I think what you want is something like Post an XML using XForms get > an XML returned, load that one is as your next XForm? > Yes I would like to see that in OO, does anyone have any idea how one > could script it. seems like it should be doable. > > >> >> Ajax's XMLHttpRequest might be another option. > Well XMLHttpRequest doesn't provide much that XForms submission > doesn't already provide I think. Ok it has access to all the http > verbs but I don't think you want a form submission to be a DELETE or a > HEAD on a URI. > >> >> This is good for the RESTful use of XML. There need >> to be ways to integrate OOo with REST and WS >> systems which are based on XML. >> > > I think that's what XForms does. > >> As for whether forms are an important part of this: >> what if the other kinds of ODF document could be >> the point from which a WS 'call', XmlHttpRequest or >> XForms-like submission is made? >> > > Well actually if you could get a response from a POST and then process > that response then that would be enough to build SOAP support upon. > > I think you're laboring under a misapprehension about XmlHttpRequest > and what it is. It just opens up all the methods of HTTP to javascript > in the browser. XForms already supports quite a few of those methods > in a declarative way, and I suppose that the various scripting apis > that exist in OO can handle whatever HTTP functionality is needed. > >> In terms of use-case the case is to be able to >> easily (with office-skills only, say) make an ODF >> document (form, spreadsheet or text document) >> which integrates with a system using XML, maybe >> web services and/or REST. >> >> > > and again: > I think that's what XForms does. > > Cheers, > Bryan Rasmussen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Stephen D. Green Partner SystML, http://www.systml.co.uk Tel: +44 (0) 117 9541606 Associate Director Document Engineering Services http://www.documentengineeringservices.com http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
