On: D3.compose – compose reusable charts and components with D3.js

[k__]

I was just looking after something like this the other day.

D3 is super for customization, but it's really really low-level.

[softawre → k__]

There are many D3 wrappers for quick starting D3. dc.js is a good one.

[awjr → softawre]

dc.js is one of those libraries that completely blows client's minds. The hard thing to do as a developer is not to try and filter the data too much. dc.js lets the end-user filter the data interactively and create their own stories, you just have to work out the questions each chart lets the user ask. http://dc-js.github.io/dc.js/

As it sits on top of crossfilter (http://square.github.io/crossfilter/) you can also do unusual things behind the scenes to the data sets. As an example, I used google maps to restrict datasets to the current map view. Worked surprisingly well. http://www.bathhacked.org/projects/hacked21-food-standards/

[elsherbini → awjr]

It looks like the link to the project on that article is down (http://www.sure-sense.com/fhrs/). Is it hosted elsewhere? I'd love to take a look.

[awjr → elsherbini]

Yeah sadly, it was a hackathon hack I repurposed afterwards for a startup I was working for. Will try and dig it out.

[placeybordeaux → softawre]

I really enjoyed using dc.js. It also rolls in crossfilter which is awesome for drilling down into data.

[sean_the_geek → placeybordeaux]

thanks for mentioning dc.js. I am looking for D3 wrappers which will make life a bit more simple. Care to mention more?

[infie → sean_the_geek]

nvd3 (https://github.com/novus/nvd3) is also pretty good.

[bbaumgar → sean_the_geek]

We've really enjoyed c3.js (http://c3js.org/). It has a wide offering of visualizations types and come with nice on-hover tooltips, which is something that I've had trouble finding anywhere else. Unfortunately it's difficult to customize their offerings, but they've covered 90% of our usecases.

[krebby → k__]

I hear this often but I'm not sure I agree. With almost all of these charting libraries you quickly run into the law of leaky abstractions. Most of the examples of things you'd want to do are written pretty clearly by Mike himself. They are easy to adapt by changing a few things around, instead of sticking with an inflexible abstraction.