<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Debugging Scripts</title>
	<atom:link href="http://forms.stefcameron.com/2006/05/05/debugging-scripts/feed/" rel="self" type="application/rss+xml" />
	<link>http://forms.stefcameron.com/2006/05/05/debugging-scripts/</link>
	<description>Building intelligent forms using Adobe LiveCycle Designer</description>
	<pubDate>Sat, 22 Nov 2008 22:58:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Stefan Cameron</title>
		<link>http://forms.stefcameron.com/2006/05/05/debugging-scripts/#comment-25592</link>
		<dc:creator>Stefan Cameron</dc:creator>
		<pubDate>Tue, 05 Aug 2008 13:51:46 +0000</pubDate>
		<guid isPermaLink="false">http://forms.stefcameron.com/blog/?p=5#comment-25592</guid>
		<description>sravya,

You're welcome!

When you preview your form in Designer or open it in Acrobat, you simply need to press "Ctrl + J" on your keyboard to see the JavaScript Console. If you're using Reader, you won't be able to see it since that feature isn't available in Reader.</description>
		<content:encoded><![CDATA[<p>sravya,</p>
<p>You&#8217;re welcome!</p>
<p>When you preview your form in Designer or open it in Acrobat, you simply need to press &#8220;Ctrl + J&#8221; on your keyboard to see the JavaScript Console. If you&#8217;re using Reader, you won&#8217;t be able to see it since that feature isn&#8217;t available in Reader.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sravya</title>
		<link>http://forms.stefcameron.com/2006/05/05/debugging-scripts/#comment-24713</link>
		<dc:creator>sravya</dc:creator>
		<pubDate>Mon, 28 Jul 2008 19:46:12 +0000</pubDate>
		<guid isPermaLink="false">http://forms.stefcameron.com/blog/?p=5#comment-24713</guid>
		<description>Hi Stefan,
thank you very much for those wonderfull scripts and tips to us new bies. i tried to use console.println abut it doesnt show anything. do i need to set anything before i use the command.please advice me
thanks</description>
		<content:encoded><![CDATA[<p>Hi Stefan,<br />
thank you very much for those wonderfull scripts and tips to us new bies. i tried to use console.println abut it doesnt show anything. do i need to set anything before i use the command.please advice me<br />
thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Groenbaek</title>
		<link>http://forms.stefcameron.com/2006/05/05/debugging-scripts/#comment-7</link>
		<dc:creator>Thomas Groenbaek</dc:creator>
		<pubDate>Sat, 06 May 2006 07:06:50 +0000</pubDate>
		<guid isPermaLink="false">http://forms.stefcameron.com/blog/?p=5#comment-7</guid>
		<description>Hi Formbuilder

Thanks for the tip with
console.println(...);

YES the scripting and debugging features in designer are limited and need more attention if Adobe wants the platform to be a serious choice for big solutions/companies.

When you are used to code completion etc. from  Visual studio, eclipse etc. you feel like you were set 5+ years back in time!

/Thomas
Jyske Bank - Denmark
</description>
		<content:encoded><![CDATA[<p>Hi Formbuilder</p>
<p>Thanks for the tip with<br />
console.println(&#8230;);</p>
<p>YES the scripting and debugging features in designer are limited and need more attention if Adobe wants the platform to be a serious choice for big solutions/companies.</p>
<p>When you are used to code completion etc. from  Visual studio, eclipse etc. you feel like you were set 5+ years back in time!</p>
<p>/Thomas<br />
Jyske Bank - Denmark</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stevex</title>
		<link>http://forms.stefcameron.com/2006/05/05/debugging-scripts/#comment-6</link>
		<dc:creator>stevex</dc:creator>
		<pubDate>Sat, 06 May 2006 02:30:02 +0000</pubDate>
		<guid isPermaLink="false">http://forms.stefcameron.com/blog/?p=5#comment-6</guid>
		<description>Another technique I use is putting a text field on the form and using it as a debug output field - setting it's text in the click event with the results of the code that's handling the click, for example.  

It's right in between app.alert and console.println - no RSI from closing the alerts, and no having to bring up the JavaScript console.   But you do have to remember to remove this field (and the code that sets it) before you're done with your form.</description>
		<content:encoded><![CDATA[<p>Another technique I use is putting a text field on the form and using it as a debug output field - setting it&#8217;s text in the click event with the results of the code that&#8217;s handling the click, for example.  </p>
<p>It&#8217;s right in between app.alert and console.println - no RSI from closing the alerts, and no having to bring up the JavaScript console.   But you do have to remember to remove this field (and the code that sets it) before you&#8217;re done with your form.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
