PDFdev is a service provided by PDFzone.com | http://www.pdfzone.com _____________________________________________________________
A lot of customers have been asking us for the ability to convert Acrobat Forms directly to HTML. We have put together an automated web service that automatically consumes an uploaded Acrobat PDF form and converts it to a corresponding set of HTML pages with links, text fields, buttons, etc. - through the browser the user sees JPG's for each PDF page and HTML fields (text, radio, etc.) appear where the Acrobat Form fields are defined.
Given this, I have two questions:
1) What kind of data binding is appropriate for such HTML form fields? The FDF model seems to require the entire form field data set be transmitted back and forth between the browser and the sever and it would also seem that reader is rather limited in what it can do regarding data saving. Doing the same thing directly in a non-Acrobat web server eliminates all the restrictions - but just eliminating restrictions doesn't seem to be enough. For example, you might want to have realtime validation happening at the field level - say a drop down that queries a database so that the choices are always current.
2) Forms seem to have the issue that the data fields they collect are time-decoupled from the server, i.e., if I create a form and later I need more data, or a check box becomes a set of radio buttons, I have no way to find all the forms in use and alter them. I am curious what sort of issues come up in this regard during actual production use of forms?
Comments??? Answers???
Thanks Todd
(post may have been duplicated... Sorry about that.)
To change your subscription: http://www.pdfzone.com/discussions/lists-pdfdev.html
