see all javascript on a form

1 view
Skip to first unread message

PhyllisJ

unread,
Jun 30, 2009, 3:28:18 PM6/30/09
to Adobe LiveCycle Developers
We are updating a form developed last year. The "owner" of the form
has made some changes and now I need to check all of the javascript
for accuracy.

Is there an easy way to see all of the javascript (and events) without
looking at each object individually?

Thanks
Phyllis

Michael Deiß

unread,
Jun 30, 2009, 3:31:55 PM6/30/09
to live...@googlegroups.com
Hi,

select the root node (the form) in the hierarchy and select in the event drop down, "All event with scripts".

Michael

-----Ursprüngliche Nachricht-----
Von: live...@googlegroups.com [mailto:live...@googlegroups.com] Im Auftrag von PhyllisJ
Gesendet: Dienstag, 30. Juni 2009 21:28
An: Adobe LiveCycle Developers
Betreff: see all javascript on a form

Parth Pandya

unread,
Jun 30, 2009, 8:20:33 PM6/30/09
to Adobe LiveCycle Developers

The way I compare old forms with new version is to compare xdp file in
a file compare utility.
This is my preference as it also highlights the field property changes
(binding, value change-in case of hard coded value, etc...)

hope it helps,

Parth Pandya
blog: http://livecyclekarma.wordpress.com

hemen.kapadia

unread,
Jul 1, 2009, 1:14:34 PM7/1/09
to Adobe LiveCycle Developers
Hi Parth,

I try to compare two versions of the same XDP file (after making a
very small script change in it) and when I try to compare it in Exam
diff I notice there are multiple changes in the file not just limited
to the script change I made.

This makes it extremely difficult to practically compare two xdp
files.

Can you throw some light or share some best practice you follow for
this.

Thanks.

-Hemen

KHinch

unread,
Jul 1, 2009, 2:00:09 PM7/1/09
to Adobe LiveCycle Developers
John Brinkman has a very useful post on "Document your Form
Template." http://blogs.adobe.com/formfeed/2009/05/document_your_form_template.html

I recently used the diagnostic form in his example to track the
evolution of scripting in one of my own forms. IMHO using
"ScriptReporter.pdf" http://blogs.adobe.com/formfeed/Samples/ScriptReporter.pdf
is a great way to evaluate a form's javascripts.

For comparing versions of a whole form I prefer comparing the two XDPs
in Notepad++ using the "Compare" plug-in.

Good luck!

Kasey

Parth Pandya

unread,
Jul 1, 2009, 7:11:16 PM7/1/09
to Adobe LiveCycle Developers
Hi Kasey,

Thanks for sharing this. I didn't know about this and haven't tried
yet. But will try that definitely.

Hemen - Even though it shows lot of things in comparison I still
prefer it so I can scan through the minor changes as well. For example
if a drop down box has a change in its value and the script is changed
a little to suites that then ignoring the drop-down box's change will
not serve the purpose. Due to those kind of situations I still skim
through the changes in compare utility.

regards,
Parth
Reply all
Reply to author
Forward
0 new messages