Sources
Help build the largest human-edited directory on the web.
Submit a site - Become an editor
Wikipedia. Licensed under the GNU Free Documentation License.
Are you an expert in this subject? Join the discussion and share your knowledge at Wikipedia.org.
Adobe LiveCycle Designer
From Wikipedia, the free encyclopedia
| LiveCycle Designer | |
 Screenshot of Adobe Designer 7.0 |
|
| Developer: | Adobe Systems |
|---|---|
| Latest release: | 7.1 / December 9, 2005 |
| OS: | Windows |
| Use: | Form Designer |
| License: | 6.0 EULA 7.0 EULA |
| Website: | www.adobe.com/products/server/adobedesigner/ |
Adobe LiveCycle Designer is a forms authoring tool published by Adobe Systems. The purpose of Designer is to be a one-stop design tool for XML forms to be rendered as PDF or HTML files.
Contents |
Designer began as a component of PerForm, an electronic forms software package created by Delrina. Delrina was bought by Symantec in 1995, which subsequently sold its Electronic Forms division to JetForm in 1996. JetForm (later renamed Accelio) was purchased by Adobe in 2002. Adobe ended the support of the Accelio version of the product in 2004.
In late 2003, Designer was redesigned and released as the Adobe Forms Designer.
In March 2004, Adobe shipped Adobe Designer 6.0 for use Adobe's Intelligent Document Platform and with version 6 of the Adobe Acrobat software. This release included support for creating dynamic forms with data propagated by the Adobe Form Server, support for the XML Data Package (XDP) file format, as well as importing existing forms from Adobe Acrobat, Adobe Output Designer, Microsoft InfoPath and Microsoft Word.
In December of 2004, Adobe released Designer as Adobe LiveCycle Designer 7.0 as part of the LiveCycle suite of products. This release added the ability to create dynamic forms that do not require the Adobe Form Server for dynamic features, tools for creating Email submissions, and the Paper Forms barcode tool. Designer 7.0 is bundled with Adobe Acrobat Professional 7.0 (on Microsoft Windows only) and available as a stand-alone product. In December of 2005, Adobe released Adobe LiveCycle Designer 7.1 as a stand-alone upgrade. Acrobat 8 shipped in November of 2006 bundled with a new version of LiveCycle Designer (version 8).
- Designer forms are structured documents with a hierarchical structure that can be converted into XML. This structure can include structure from XML Schema and example XML files.
- Designer forms can be saved as PDF files or XDP files. XDP files are used by the Adobe LiveCycle Form Server to render files to PDF or HTML as needed.
- PDF forms made in Designer can be designed to be dynamic (changing layout in response to data propagated from other sources), interactive (capable of accepting user input) or both. As of Designer 7.0, dynamic features of these PDF forms can be manipulated by the Adobe Form Server during the rendering process, or by the Adobe Acrobat/Acrobat Reader client during viewing.
- Designer allows JavaScript to be embedded into a form, allowing programmatic changes to the form layout as well as communication with various data sources (SOAP, OLEDB).
- Besides JavaScript, Designer includes a proprietary scripting language called FormCalc, designed to be a simple language for users familiar with spreadsheet calculations.
- Viewing PDF forms made with Designer requires Acrobat/Adobe Reader 6.0.2 or later.
- PDF forms made with Designer cannot be edited in Adobe Acrobat, only viewed.
- Some features of Designer forms are dependent on 'user rights' activated through the Adobe LiveCycle Reader Extensions server product.
- Acrobat has been able to make forms since Acrobat 3.0, and there are some third party tools which can work with them in addition to Adobe software. However, these are a type of form now called "acroforms". Forms created by Designer are an incompatible type (commonly "XFA forms") and are not in general compatible with existing non-Adobe software. Owners of Acrobat 7.0 Professional have the choice of making acroforms directly, or using the bundled (on Windows) copy of Designer to create XFA forms.
- When a form object is bound to an xml node, the value from that node may only be extracted once. If several objects share the same binding, only the first object will receive the node value when the form is processed.
- There are limitations in the ability of Designer to parse HTML and display it in a form; Designer cannot handle a number of fundamental tags, including ordered list, unordered list and tables.[citation needed]