<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>PerformancePointy: Wade Dorrell's MSDN Blog : google</title><link>http://blogs.msdn.com/wadedor/archive/tags/google/default.aspx</link><description>Tags: google</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Google charting</title><link>http://blogs.msdn.com/wadedor/archive/2008/05/05/google-charting.aspx</link><pubDate>Mon, 05 May 2008 20:59:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8461050</guid><dc:creator>Wade Dorrell</dc:creator><slash:comments>4</slash:comments><comments>http://blogs.msdn.com/wadedor/comments/8461050.aspx</comments><wfw:commentRss>http://blogs.msdn.com/wadedor/commentrss.aspx?PostID=8461050</wfw:commentRss><description>&lt;p&gt;I was toying around with &lt;a href="http://www.friendfeed.com/waded"&gt;FriendFeed&lt;/a&gt; and discovered Google's charting engine. Mmm, pie:&lt;/p&gt;  &lt;p&gt;&lt;img src="http://chart.apis.google.com/chart?chs=415x200&amp;amp;chd=s:9P&amp;amp;chl=Blog|Flickr&amp;amp;cht=p&amp;amp;chco=71ab0b" /&gt;&lt;/p&gt;  &lt;p&gt;The engine can render Google Analytics-esque sparklines too. The simplicity and accessibility of this &lt;a href="http://code.google.com/apis/chart"&gt;API&lt;/a&gt; is impressive... it's all in the URL.&lt;/p&gt;  &lt;p&gt;Now, I'm a bit agitated by this discovery, as years ago at ProClarity Greg &amp;amp; I built very similar to this API for doing sparklines, bullet graphs, and other datawords. I haven't shared it with you yet, and I should have. While it was no complete charting engine, and neither is Google's, our implementation was all of 300 lines of C#... so you could probably build &amp;amp; modify the implementation for your own specific needs pretty easily. Please let me know if you want it, and I'll throw it up on &lt;a href="http://www.codeplex.com"&gt;Codeplex&lt;/a&gt;.&lt;/p&gt;  &lt;p&gt;The major downside of our &amp;amp; Google's architecture is your data is relayed in the GET URL. It's getting replicated in logs. In Google's case, it's sent naked across the Internet (invalid certificate/no HTTPS), and aggregated in Google's data centers. According to the TOS this service cannot be relied on for uptime or continued compatibility. It will break for FriendFeed someday. Of course, free isn't always free! There's definitely some reasons to figure out how to host your own implementation on LAN &amp;amp; with security if you're using this for sensitive data or critical applications, and I should have shared it long ago.&lt;/p&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8461050" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/wadedor/archive/tags/proclarity/default.aspx">proclarity</category><category domain="http://blogs.msdn.com/wadedor/archive/tags/google/default.aspx">google</category><category domain="http://blogs.msdn.com/wadedor/archive/tags/charts/default.aspx">charts</category><category domain="http://blogs.msdn.com/wadedor/archive/tags/pie/default.aspx">pie</category><category domain="http://blogs.msdn.com/wadedor/archive/tags/visualizations/default.aspx">visualizations</category><category domain="http://blogs.msdn.com/wadedor/archive/tags/sparklines/default.aspx">sparklines</category></item></channel></rss>