<?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: How To View JSON in a Pretty Way</title>
	<atom:link href="http://peterkellner.net/2009/11/06/formatting-json-best-tool/feed/" rel="self" type="application/rss+xml" />
	<link>http://peterkellner.net/2009/11/06/formatting-json-best-tool/</link>
	<description>Microsoft Focussed, JavaScript (ExtJS, SenchaTouch &#38; Windows 8 Metro)</description>
	<lastBuildDate>Wed, 08 Feb 2012 21:38:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: DBJ</title>
		<link>http://peterkellner.net/2009/11/06/formatting-json-best-tool/comment-page-1/#comment-27636</link>
		<dc:creator>DBJ</dc:creator>
		<pubDate>Wed, 19 May 2010 14:43:03 +0000</pubDate>
		<guid isPermaLink="false">http://peterkellner.net/2009/11/06/formatting-json-best-tool/#comment-27636</guid>
		<description>Well this certainly works. Also I looked &quot;under the bonet&quot;. Very old-fashioned javascript, globals, no closure, etc. jQuery would certainly streamline a lot of code inside. As also will: ECMA Script 5 objects detection and usage if present. Of which most obvious  omission is not using native JSON object, if available. Which in turn does much better JSON syntax check than simple: eval(&quot;[&quot; + json + &quot;]&quot;), currently &quot;in there&quot;... CSS also leaves much space for improvement.

But certainly this works very well for a lot of people.</description>
		<content:encoded><![CDATA[<p>Well this certainly works. Also I looked &#8220;under the bonet&#8221;. Very old-fashioned javascript, globals, no closure, etc. jQuery would certainly streamline a lot of code inside. As also will: ECMA Script 5 objects detection and usage if present. Of which most obvious  omission is not using native JSON object, if available. Which in turn does much better JSON syntax check than simple: eval(&#8220;[" + json + "]&#8220;), currently &#8220;in there&#8221;&#8230; CSS also leaves much space for improvement.</p>
<p>But certainly this works very well for a lot of people.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cyril Gupta</title>
		<link>http://peterkellner.net/2009/11/06/formatting-json-best-tool/comment-page-1/#comment-25558</link>
		<dc:creator>Cyril Gupta</dc:creator>
		<pubDate>Sat, 07 Nov 2009 05:24:35 +0000</pubDate>
		<guid isPermaLink="false">http://peterkellner.net/2009/11/06/formatting-json-best-tool/#comment-25558</guid>
		<description>Nice formatter... Color coding is excellent.</description>
		<content:encoded><![CDATA[<p>Nice formatter&#8230; Color coding is excellent.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced)
Database Caching 1/13 queries in 0.004 seconds using disk

Served from: peterkellner.net @ 2012-02-10 05:41:46 -->
