Form Builder Aims.

> I'm trying to build my mind map of what is your intent for the form  
> builder...please give me any advice.
>
> I would like to use the builder in order to speed up development of  
> my forms, and to obtain feedback from clients. It means that I would  
> like this roadmap more or less:
>
> -Open the builder and make a prototype form.
> -Publish it and give the url to the clients.
> -Obtain feedback, modify it, publish and obtain feedback until accept.
> -Take the definitive form and integrate it in my application.
>
> Would you please tell me if this is in line with your view or  
> intent? I have read several threads of the mailing list and i don't  
> have a clear idea...it seems that I have to use the form runner and  
> this doesn't seem to be suitable...maybe you have to produce a kind  
> of export that could be run on sandbox or any other application  
> context....
>
> greetings,
>
> rich
>
> --
> You receive this message as a subscriber of the [hidden email]  
> mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws

> Rich,
>
> I think you scenario is perfect.
>
> Yes, you have to use Form Runner, but I don't think this should be a  
> problem: you can still send out a link to your published form. This  
> assumes you have Orbeon Forms deployed in a place where your client  
> can access it.
>
> -Erik

> > no problem in order to show it to the client, but the problem is the  
> > last step:
> >
> >>> -Take the definitive form and integrate it in my application.
> >
> > I want to have and standalone form in order to execute it in my  
> > application, not needing form runner....how?
>
> Currently, you do need Form Runner. You could imagine exporting the  
> form after it has gone through Form Runner's transformations but  
> before it reaches the XForms engine. That may work. The form would  
> then look exactly as if it had gone through Form Runner though.
>
> -Erik

> > could you suggest a hack for me to do that?
>
> Check the "Edit document" page flow entry for the Form Runner app. You  
> would have to create a new page flow entry for the export. You pretty  
> much want the same functionality as this, except you don't want the  
> XForms engine to run on the output. You could create just a page model  
> putting together the "Edit document" page model and view, and then  
> serialize that out yourself instead of going through the epilogue.
>
> -Erik