The process from specification to finished form starts with developing the form in the Adobe LiveCycle Designer. In the Designer, the form is viewed as consisting of three main parts; the graphical layout of the form, a hierarchical structure of logical form elements and the form scripts. The form layout is created through a drag-and-drop, WYSIWYG interface. Form elements are selected from a library and dragged to the desired position in the form. The standard library in the Designer contains all the fields and elements typically found in forms; text fields, radio buttons, checkboxes and drop-down lists, as well as a selection of graphical and structural elements like lines, curves, image fields and tables which can be used to create the desired visual representation . The form elements can be positioned freely by the pixel or by applying various positioning tools. All form elements can be tailored to using the desired font, style and colours. Furthermore, groups of elements can be grouped into "subforms" - logical and structural units of form elements. Both customised form elements and subforms can easily be stored in a library for future use.
News: Article: Implementing e-forms with Adobe LiveCycle Forms
Håvard Nesvold has written "Implementing e-forms with Adobe LiveCycle Forms," describing how to use LiveCycle to implement client-side forms with active content - much as Ajax does today, except with more content types, and with the assistance of a page designer.
- Posted by: Joseph Ottinger
- Posted on: September 04 2007 17:48 EDT
has anyone compared adobe forms with infopath or xforms ? what would you recommend ? - Ron