<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Debug/Logging Client-Side &#8211; Part 1</title>
	<atom:link href="http://www.flexer.info/2007/10/24/debuglogging-client-side/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.flexer.info/2007/10/24/debuglogging-client-side/</link>
	<description>flex developers web corner</description>
	<lastBuildDate>Wed, 18 Jan 2012 13:28:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Client-Side Flex Logging with Shared Object</title>
		<link>http://www.flexer.info/2007/10/24/debuglogging-client-side/comment-page-1/#comment-1674</link>
		<dc:creator>Client-Side Flex Logging with Shared Object</dc:creator>
		<pubDate>Tue, 11 Aug 2009 15:29:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.flexer.info/2007/10/24/debuglogging-client-side/#comment-1674</guid>
		<description>[...] Having your app keep a detailed log can be indispensable for figuring out tricky user-reported bugs. This is easy on the server-side, where you can use any logging framework or just write to a file. Flash includes the trace function, which is useful while developing, but nearly impossible to get from an end-user. Flex, however, has a good logging api that lets you put log statements anywhere you want. I’ve always wanted the interface to be as easy as trace, so I write a couple of scripts to make it easier. [...]</description>
		<content:encoded><![CDATA[<p>[...] Having your app keep a detailed log can be indispensable for figuring out tricky user-reported bugs. This is easy on the server-side, where you can use any logging framework or just write to a file. Flash includes the trace function, which is useful while developing, but nearly impossible to get from an end-user. Flex, however, has a good logging api that lets you put log statements anywhere you want. I’ve always wanted the interface to be as easy as trace, so I write a couple of scripts to make it easier. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FLEX{er} &#187; Blog Archive &#187; Debug/Logging Client-Side Part 2</title>
		<link>http://www.flexer.info/2007/10/24/debuglogging-client-side/comment-page-1/#comment-10</link>
		<dc:creator>FLEX{er} &#187; Blog Archive &#187; Debug/Logging Client-Side Part 2</dc:creator>
		<pubDate>Mon, 29 Oct 2007 16:23:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.flexer.info/2007/10/24/debuglogging-client-side/#comment-10</guid>
		<description>[...] my previous  post I started to talk about how you can see the same trace messages you were used from developing [...]</description>
		<content:encoded><![CDATA[<div style="padding: 1em; background: #d3e1ef; /* border: dotted 1px #777777; */">
<p>[...] my previous  post I started to talk about how you can see the same trace messages you were used from developing [...]</p>
</div>
]]></content:encoded>
	</item>
</channel>
</rss>

