Are these really performance extensions? They look more like extensions to simplify the creation of common charts like geo, stacked bar graphs, etc.
edit: The library looks pretty slick though--I like the fluent interface for describing a chart, and how it doesn't try to hide the lower level D3 functions. Here's a an example I found on their github: https://github.com/alexandersimoes/d3plus/blob/master/exampl...
It does seem to be primarily for quick visualization of common use cases. I was a little disappointed because I've been meaning to do some research in speeding up my d3 visualizations, although this seems really cool none the less.
I'm not convinced this would be faster over my current knowledge of d3 but it's pretty solid and if you want to avoid common pitfalls it might work for you.
Yeah I thought it was about performance also. One thing I've never gotten around to was really look at the d3 code and see how renderings are done. Does D3 re-render on every property change? Or does it save all the changes and render once at the end.
A quick glance at D3's source code confirms what I suspected: all it does is call setAttributeNS on the DOM. So the re-rendering isn't really its concern, but the browser's.
As for performance, I believe the focus is on the user's performance, not the computer's.
14 comments
[ 0.23 ms ] story [ 54.9 ms ] threadI _know_ I should use it, but every time I try to, I lose myself in it, and end up using Flot instead :(
edit: The library looks pretty slick though--I like the fluent interface for describing a chart, and how it doesn't try to hide the lower level D3 functions. Here's a an example I found on their github: https://github.com/alexandersimoes/d3plus/blob/master/exampl...
As for performance, I believe the focus is on the user's performance, not the computer's.
http://nvd3.org
Not so much performance extensions as simplifications... hopefully the title of the post can be adjusted.