<?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: Generating charts from accessible data tables and vice versa using the Google Charts API</title>
	<link>http://www.wait-till-i.com/2008/01/08/generating-charts-from-accessible-data-tables-using-the-google-charts-api/</link>
	<description>Random notes by Chris Heilmann</description>
	<pubDate>Mon, 12 May 2008 16:19:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Robin Winslow</title>
		<link>http://www.wait-till-i.com/2008/01/08/generating-charts-from-accessible-data-tables-using-the-google-charts-api/#comment-7386</link>
		<dc:creator>Robin Winslow</dc:creator>
		<pubDate>Tue, 01 Apr 2008 09:56:01 +0000</pubDate>
		<guid>http://www.wait-till-i.com/2008/01/08/generating-charts-from-accessible-data-tables-using-the-google-charts-api/#comment-7386</guid>
		<description>There seems to be a problem with the Google Chart API whereby it can only handle up to three digit numbers. If it has more than 3 digits it just ignores the last digit.

Try it with 10 and 1000:
http://chart.apis.google.com/chart?cht=p3&#38;chs=450x150&#38;chd=t:10,1000
You will find it looks exactly the same as 10 and 100:
http://chart.apis.google.com/chart?cht=p3&#38;chs=450x150&#38;chd=t:13,100
And is therefore wrong.

So, if I get around to it I will put something in the JS to check if any of the pieces of data in a chart exceed 3 digits, and if they do, reduce all data by the required number of digits to bring all data within 3 digits, so that everything remains proportionally correct (10 and 1000 would translate to 1 and 100 rather than 10 and 100 as Google would do automatically).

If I do this I'll post the next script here.

Robin.</description>
		<content:encoded><![CDATA[<p>There seems to be a problem with the Google Chart API whereby it can only handle up to three digit numbers. If it has more than 3 digits it just ignores the last digit.</p>
<p>Try it with 10 and 1000:<br />
<a href="http://chart.apis.google.com/chart?cht=p3&#038;chs=450x150&#038;chd=t:10,1000" rel="nofollow">http://chart.apis.google.com/chart?cht=p3&#038;chs=450x150&#038;chd=t:10,1000</a><br />
You will find it looks exactly the same as 10 and 100:<br />
<a href="http://chart.apis.google.com/chart?cht=p3&#038;chs=450x150&#038;chd=t:13,100" rel="nofollow">http://chart.apis.google.com/chart?cht=p3&#038;chs=450x150&#038;chd=t:13,100</a><br />
And is therefore wrong.</p>
<p>So, if I get around to it I will put something in the JS to check if any of the pieces of data in a chart exceed 3 digits, and if they do, reduce all data by the required number of digits to bring all data within 3 digits, so that everything remains proportionally correct (10 and 1000 would translate to 1 and 100 rather than 10 and 100 as Google would do automatically).</p>
<p>If I do this I'll post the next script here.</p>
<p>Robin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blogger</title>
		<link>http://www.wait-till-i.com/2008/01/08/generating-charts-from-accessible-data-tables-using-the-google-charts-api/#comment-7344</link>
		<dc:creator>Blogger</dc:creator>
		<pubDate>Wed, 26 Mar 2008 09:21:28 +0000</pubDate>
		<guid>http://www.wait-till-i.com/2008/01/08/generating-charts-from-accessible-data-tables-using-the-google-charts-api/#comment-7344</guid>
		<description>This API is great,
Google APIs are amazing,
I had implement a UI editor for Google Charts, you can access it at 
http://chartgen.blogspot.com</description>
		<content:encoded><![CDATA[<p>This API is great,<br />
Google APIs are amazing,<br />
I had implement a UI editor for Google Charts, you can access it at <br />
<a href="http://chartgen.blogspot.com" rel="nofollow">http://chartgen.blogspot.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Hirst</title>
		<link>http://www.wait-till-i.com/2008/01/08/generating-charts-from-accessible-data-tables-using-the-google-charts-api/#comment-7246</link>
		<dc:creator>Tony Hirst</dc:creator>
		<pubDate>Fri, 07 Mar 2008 09:58:59 +0000</pubDate>
		<guid>http://www.wait-till-i.com/2008/01/08/generating-charts-from-accessible-data-tables-using-the-google-charts-api/#comment-7246</guid>
		<description>Hi 
I was just have a quick look at the UN data browser (e.g. http://data.un.org/Data.aspx?q=london&#38;d=CDB&#38;f=srID:6850 ) and it stuck me that you script could be used as part of a bookmarklet powered app that could:

1) pop-up a list of tables in a page;
2) allow you to select (and maybe preview the first 2-3 rows) of each column in a given table
3) use the selected columns to provide the chart data

tony</description>
		<content:encoded><![CDATA[<p>Hi <br />
I was just have a quick look at the UN data browser (e.g. <a href="http://data.un.org/Data.aspx?q=london&#038;d=CDB&#038;f=srID:6850" rel="nofollow">http://data.un.org/Data.aspx?q=london&#038;d=CDB&#038;f=srID:6850</a> ) and it stuck me that you script could be used as part of a bookmarklet powered app that could:</p>
<p>1) pop-up a list of tables in a page;<br />
2) allow you to select (and maybe preview the first 2-3 rows) of each column in a given table<br />
3) use the selected columns to provide the chart data</p>
<p>tony</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stéphane Deschamps</title>
		<link>http://www.wait-till-i.com/2008/01/08/generating-charts-from-accessible-data-tables-using-the-google-charts-api/#comment-6918</link>
		<dc:creator>Stéphane Deschamps</dc:creator>
		<pubDate>Mon, 21 Jan 2008 10:10:46 +0000</pubDate>
		<guid>http://www.wait-till-i.com/2008/01/08/generating-charts-from-accessible-data-tables-using-the-google-charts-api/#comment-6918</guid>
		<description>I've pondered a few days before commenting, but I have the impression that this kind of script is the last point that was needed to make the longdesc attribute definitely history.

I don't mean you've nailed the coffin yourself, but I get the idea that some people will go "Oh, we don't need longdesc, now that there are simple and elegant solutions like Chris's".

Shouldn't we somewhere be clear about the very specific usage of your scripts? I fear the pseudo-magic effect at work here. What do you think?</description>
		<content:encoded><![CDATA[<p>I've pondered a few days before commenting, but I have the impression that this kind of script is the last point that was needed to make the longdesc attribute definitely history.</p>
<p>I don't mean you've nailed the coffin yourself, but I get the idea that some people will go "Oh, we don't need longdesc, now that there are simple and elegant solutions like Chris's".</p>
<p>Shouldn't we somewhere be clear about the very specific usage of your scripts? I fear the pseudo-magic effect at work here. What do you think?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.wait-till-i.com/2008/01/08/generating-charts-from-accessible-data-tables-using-the-google-charts-api/#comment-6907</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Thu, 17 Jan 2008 17:13:09 +0000</pubDate>
		<guid>http://www.wait-till-i.com/2008/01/08/generating-charts-from-accessible-data-tables-using-the-google-charts-api/#comment-6907</guid>
		<description>@alastairc aye, check out the YUI blog today: http://yuiblog.com/blog/2008/01/17/tables-and-charts/</description>
		<content:encoded><![CDATA[<p>@alastairc aye, check out the YUI blog today: <a href="http://yuiblog.com/blog/2008/01/17/tables-and-charts/" rel="nofollow">http://yuiblog.com/blog/2008/01/17/tables-and-charts/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
