In fact, nearly 1/3 of the data transferred for the first graph is javascript[0].
The issues Google ran into were as it gets popular you need a more server horse power, and the work of keeping things secure is pretty high.
That said I always enjoyed using chartserver :-) so I presume I would enjoy using this. But what I'd really like is a package for python or perl I could load up behind an nginx instance and make this a local feature.
We revisit the deprecation of Chartserver every couple of months (I believe it's had two stays of execution), so there might be some life left in that old code.
Services like this, are one of the things that keeps up 'Google's not just in it for the money' cred, I'm going to be really sorry to see it go.
Isn't that right there an example, or warning, or admonition, or something, suggesting that you not use external services for essential features? I know that no page is likely to last more than five years, but there are going to be many pages that outlast services like this.
Or am I missing the target use case?
Check out: http://smashrun.com/chris.lukic/overview It uses both D3 and ChartServer, but there's no way I'll ever get the page load to something comparable using only d3.
I think that's a significant difference, in that the <object> variant of this API has the potential for access to the chart elements for styling and interactivity.
Having recently rediscovered the non-joy of putting somebody else's javascript on a page (in that case WebRing) I am a bit gun shy of the whole model[0].
I really like the idea of 'server driven charts' for easy web pages and illustration. But I would rather have it be something I could put on an Raspberry Pi in my network so that I didn't have to worry either about the privacy issues or it going away (as Chartserver has been trying to do :-).
[0] Imagine what will happen if placekitten.com gets sold to some porn aggregator.
I can't think of many reasons for building them serverwise.. except for when you don't have access to javascript or you are limited by the power as well.
<img src="//api.chartspree.com/bar.svg?Foo=1,1,2,3,5">
However the actual embedded code for the example and the resultant chart is:
<img src="//api.chartspree.com/bar.svg?Foo=1,1,2,3,6">
My immediate reaction to seeing the wrong chart being displayed for some example code was that your system just didn't work properly.
As this is the first thing anyone sees when visiting the project, it might be a good thing to change.
For example, sometimes this is funny, and sometimes it isn't, depending on which label is assigned to which color (seemingly random).
Edit: I guess Middleman isn't the only SSG :)
- Let me choose the colors
- Let me add or remove bullets on the line charts
- Let me control the axes
- Let me add a grid
Love it! Keep it up.
but the chart shows the last bar going to six.
The URL makes it apparent that it's just a typo, but it's the literally the first thing on the page :)
http://api.chartspree.com/bar.svg?Foo=1,1,2,3,6&_height=250p...
I could see this going viral on sites like Pinterest or Tumblr, but I found that when I added this into Tumblr, it wouldn't save the post.
I like it.
