<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: The easiest way to view Flex/Apollo trace output</title>
	<link>http://caleb.org/blog/uncategorized/the-easiest-way-to-view-flexapollo-trace-output/</link>
	<description></description>
	<pubDate>Thu, 16 Oct 2008 07:12:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: tom hensel</title>
		<link>http://caleb.org/blog/uncategorized/the-easiest-way-to-view-flexapollo-trace-output/#comment-5483</link>
		<dc:creator>tom hensel</dc:creator>
		<pubDate>Thu, 05 Apr 2007 10:42:00 +0000</pubDate>
		<guid>http://caleb.org/blog/uncategorized/the-easiest-way-to-view-flexapollo-trace-output/#comment-5483</guid>
		<description>instead of cygwin tail i'd recommend
http://tailforwin32.sourceforge.net/

regards,
tom</description>
		<content:encoded><![CDATA[<p>instead of cygwin tail i&#8217;d recommend<br />
<a href="http://tailforwin32.sourceforge.net/" rel="nofollow">http://tailforwin32.sourceforge.net/</a></p>
<p>regards,<br />
tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Caleb</title>
		<link>http://caleb.org/blog/uncategorized/the-easiest-way-to-view-flexapollo-trace-output/#comment-5477</link>
		<dc:creator>Caleb</dc:creator>
		<pubDate>Thu, 05 Apr 2007 03:19:39 +0000</pubDate>
		<guid>http://caleb.org/blog/uncategorized/the-easiest-way-to-view-flexapollo-trace-output/#comment-5477</guid>
		<description>Lanny,

Honestly, I have no problem with the debugger built into the Flex Builder IDE.  I love Flex Builder 2, and I feel fortunate to be one of the lucky people who has an opportunity to use it everyday.  However, it's important to remember the free, open alternatives people have when developing.  I was speaking from the perspective of someone using Eclipse and the free version of the Flex 2 SDK to build projects.  This certainly isn't the most thorough debugging mechanism... just a simple approach that allows you to perform a fundamental task.  At any rate, thanks for the comment :-)</description>
		<content:encoded><![CDATA[<p>Lanny,</p>
<p>Honestly, I have no problem with the debugger built into the Flex Builder IDE.  I love Flex Builder 2, and I feel fortunate to be one of the lucky people who has an opportunity to use it everyday.  However, it&#8217;s important to remember the free, open alternatives people have when developing.  I was speaking from the perspective of someone using Eclipse and the free version of the Flex 2 SDK to build projects.  This certainly isn&#8217;t the most thorough debugging mechanism&#8230; just a simple approach that allows you to perform a fundamental task.  At any rate, thanks for the comment <img src='http://caleb.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Weyert de Boer</title>
		<link>http://caleb.org/blog/uncategorized/the-easiest-way-to-view-flexapollo-trace-output/#comment-5474</link>
		<dc:creator>Weyert de Boer</dc:creator>
		<pubDate>Thu, 05 Apr 2007 02:40:41 +0000</pubDate>
		<guid>http://caleb.org/blog/uncategorized/the-easiest-way-to-view-flexapollo-trace-output/#comment-5474</guid>
		<description>Nice one!</description>
		<content:encoded><![CDATA[<p>Nice one!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lanny</title>
		<link>http://caleb.org/blog/uncategorized/the-easiest-way-to-view-flexapollo-trace-output/#comment-5471</link>
		<dc:creator>Lanny</dc:creator>
		<pubDate>Thu, 05 Apr 2007 00:33:17 +0000</pubDate>
		<guid>http://caleb.org/blog/uncategorized/the-easiest-way-to-view-flexapollo-trace-output/#comment-5471</guid>
		<description>What do you find cumbersome about the built in debugger in flex?  Besides having to toggle between the web browser and flex, I find it quite easy to use, particularly since you can double-click errors and go directly to the offending code...</description>
		<content:encoded><![CDATA[<p>What do you find cumbersome about the built in debugger in flex?  Besides having to toggle between the web browser and flex, I find it quite easy to use, particularly since you can double-click errors and go directly to the offending code&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
