<?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: Reviewing an NYTimes Infographic</title>
	<atom:link href="http://newswithnumbers.com/2010/03/03/reviewing-an-nytimes-infographic/feed/" rel="self" type="application/rss+xml" />
	<link>http://newswithnumbers.com/2010/03/03/reviewing-an-nytimes-infographic/</link>
	<description>Learning More By Reading Less</description>
	<lastBuildDate>Fri, 13 Aug 2010 01:53:06 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: numbersguy</title>
		<link>http://newswithnumbers.com/2010/03/03/reviewing-an-nytimes-infographic/comment-page-1/#comment-437</link>
		<dc:creator>numbersguy</dc:creator>
		<pubDate>Wed, 03 Mar 2010 19:04:27 +0000</pubDate>
		<guid isPermaLink="false">http://newswithnumbers.com/?p=1262#comment-437</guid>
		<description>Hi Emily,

I agree completely. When I envisioned this I thought the original NYTimes graphic would be small enough to have the articles appear exclusively on one side and the treemap on the other. Instead of redoing the NYTimes graphic from scratch I decided to run with it as is and made the text boxes as you see them.

I may modify some of the mock articles to be headlines just to get that point across too. I&#039;m not against it, just didn&#039;t think to include it in the sample.

I also envisioned legislators using this sort of technique in an augmented reality sort of way... Imagine being in your seat in congress while another rants on about excessive spending on a budget item. How cool would it be if the listening legislator could hold up their iPhone, capture some audio and have an app voice recognize the section of the budget under discussion, display the treemap and ...</description>
		<content:encoded><![CDATA[<p>Hi Emily,</p>
<p>I agree completely. When I envisioned this I thought the original NYTimes graphic would be small enough to have the articles appear exclusively on one side and the treemap on the other. Instead of redoing the NYTimes graphic from scratch I decided to run with it as is and made the text boxes as you see them.</p>
<p>I may modify some of the mock articles to be headlines just to get that point across too. I&#8217;m not against it, just didn&#8217;t think to include it in the sample.</p>
<p>I also envisioned legislators using this sort of technique in an augmented reality sort of way&#8230; Imagine being in your seat in congress while another rants on about excessive spending on a budget item. How cool would it be if the listening legislator could hold up their iPhone, capture some audio and have an app voice recognize the section of the budget under discussion, display the treemap and &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emily Merwin</title>
		<link>http://newswithnumbers.com/2010/03/03/reviewing-an-nytimes-infographic/comment-page-1/#comment-436</link>
		<dc:creator>Emily Merwin</dc:creator>
		<pubDate>Wed, 03 Mar 2010 18:54:15 +0000</pubDate>
		<guid isPermaLink="false">http://newswithnumbers.com/?p=1262#comment-436</guid>
		<description>Great idea! I love the idea of tying the particular items to stories about them - but I&#039;m not sure I necessarily want to see the WHOLE story as a mouseover - it crowds out the other info (change from last year), would be awkward for longer stories, and what do you do if you have more than one related story? A link (with a descriptive title) would suite me just fine. Then you run into the problem of how can they click on the link since it follows your mouse and release events are already doing something else, and anything more complicated than that might not be so user friendly... but it&#039;s something to think about!</description>
		<content:encoded><![CDATA[<p>Great idea! I love the idea of tying the particular items to stories about them &#8211; but I&#8217;m not sure I necessarily want to see the WHOLE story as a mouseover &#8211; it crowds out the other info (change from last year), would be awkward for longer stories, and what do you do if you have more than one related story? A link (with a descriptive title) would suite me just fine. Then you run into the problem of how can they click on the link since it follows your mouse and release events are already doing something else, and anything more complicated than that might not be so user friendly&#8230; but it&#8217;s something to think about!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
