Check this out: My colleague Trevor Ward, developer on the Form Guide Team, has just posted a very cool sample of an AIR app running a Form Guide complete with data and an embedded PDF on the LiveCycle Form Guide blog. Please keep in mind that it’s just a proof-of-concept but it should give you enough to go on to build your own solution if you’ve been wondering if/how this could be done.
It seems that calculating totals in an expandable table with a dynamic/repeatable row is a hot topic lately so I thought I would post a tutorial on how to build a simple table which represents a purchase order where you can add and remove line items and various totals are automatically calculated.
Before we get started, you’ll need Designer 7.1 and Acrobat/Reader 7.0.5 at minimum to run through this tutorial. I will be using Designer 8.2 and Acrobat/Reader 9.0 to do the tutorial so it’s possible some of the UI may have changed slightly since the 7.1/7.05 versions.
Since I spend most of my free time outside of work and electronic forms on my road bike and training for running races, I thought I would share a few pictures of the 10k I ran at the very first Ottawa Winterman race today, Feb 22, 2009. In true Canadian form, we ran outside in the blowing snow. Thankfully it wasn’t very cold: About -3C with a windchill around -10C. I wasn’t as serious about this race as with others so I was just out to have fun and I still managed a respectable 50:14 finish time despite the greasy, slushy road conditions!
The recording of the Acrobat User Community eSeminar on Advanced Forms and LiveCycle Designer by Easel Solution’s Angie Okamoto is now available for viewing. Angie demonstrates advanced concepts in creating dynamic forms with LC Designer and you can also see all of the Q&A comment threads between the attendees and the team of specialists answering the questions.
Let me put it simply: I got burned by using a particular syntax to check the existence of a field inside a subform object due to form compatibility settings in LiveCycle Designer 8.2.
It started with a form I had created using Designer 8.1 which was set to target Acrobat 8.1/XFA 2.6. Later-on, I installed Designer 8.2 and wanted to update my form to target Acrobat 9/XFA 2.8.
In my form, I had a script object with various functions that used the following syntax to test the existence of a field inside a subform object which was passed-in to these functions as a parameter:
if (subformObj.someField)The result of this was what I expected: If ‘someField’ existed inside ‘subformObj’, the IF statement would evaluate to ‘true’; if it didn’t, it would evaluate to ‘false’. According to the rules of dynamic properties in JavaScript, this was all fine and dandy.
