Talk:Adobe LiveCycle Designer

Learn more about this page

This is the talk page for discussing improvements to the Adobe LiveCycle Designer article.
This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

Computing: Software Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software (assessed as Low-importance).

Tip: Anchors are case-sensitive in most browsers.

This article links to one or more target anchors that no longer exist.

[[Portable Document Format#AcroForms|PDF forms]] The anchor (#AcroForms) has been deleted.

Please help fix the broken anchors. You can remove this template after fixing the problems. | Reporting errors

Untitled edit

Latest comment: 16 years ago2 comments2 people in discussion

The article implies that LiveCycle Designer has a heritage that traces back to PerForm. This is false.

The Delrina products were distinct with no relationship to the heritage of LiveCycle Designer. LiveCycle Designer roots, in terms of many of personnel and primary location of development, reach back through the Accelio and JetForm years; and, JetForm's products were distinct from Delrina's, and (if we must go way back) evolved from a product family from Indigo Software in the 1980's, before going public in the early 90's and renaming the company JetForm.

Yes, JetForm/Accelio did have a product called FormFlow which was a product name JetForm obtained the rights too via acquiring the Delrina forms products. However, the only similarity between the JetForm/Accelio FormFlow product and the Delrina FormFlow product was the name.

The article also says that "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." This is untrue. Multiple form objects can bind to the same XML node.

The article says "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." However, this statement does not inform the reader of the context for the use of HTML, which is for representing formatted text within individual form object, not as a generalized approach to structured content. Without this context the reader may infer that tables are not a capability for forms created with LiveCycle Designer, when this is not true. LiveCycle Designer does not utilize HTML to describe tables, instead using the underlying XFA markup to describe tables and tabular layout.

Gavin mckenzie 00:39, 19 June 2007 (UTC)Reply

Sounds great - make the changes! :) Blade 17:17, 19 June 2007 (UTC)Reply

Hey Gavin - "Multiple form objects can bind to the same XML node." how can they be bound to the same xml node and still display the data? I actually ran into this problem and you're the first one who suggest it is doable - so please describe how it is done...

Add topic