Hacker News new | past | comments | ask | show | jobs | submit login

Since it's not clear from the link, I'll clarify that this refers to resampling for map (cartographic) projections. For more on our recent work on extended projections, see the geo/projections plugin:

https://github.com/d3/d3-plugins/tree/master/geo/projection

And more cool mapping demos here:

http://bl.ocks.org/jasondavies http://bl.ocks.org/mbostock




Mike, thanks for all the work you and others do on D3.

This week, I attended the first meeting of the D3.js meetup here in NYC http://www.meetup.com/NYC-D3-JS/ .

If you're ever on this coast, I know there are at least 190 other people who appreciate the work you do and would love to see you present on it.


I spent a good portion of my internship last summer working with d3 at Splunk, just wanted to say thanks for the cool framework. I love the "data", "enter", and "exit" calls, it's a really great way of thinking about data binding.

I'd like to try to incorporate it into something other than svg/canvas visualizations too, maybe just a normal web app or something, do you know of people using it like that?

Thanks, again!


Thanks! Yeah, you can definitely use D3 outside of data visualization; the data-join pattern is useful whenever you want to generate a DOM from data and keep the DOM up-to-date as data changes.

D3 also provides custom event dispatching for loosely-coupled components:

https://github.com/mbostock/d3/wiki/Internals#wiki-d3_dispat...

That said, there are higher-level abstractions (e.g., Backbone and Ember) that are explicitly designed for this purpose, and provide useful ways of structuring big applications into separable components. Depending on the size of the application you're trying to build, you might find those useful as well, perhaps in addition to D3.


It works great to build tables and tree's of div tags. Its node manipulation aspect is awesome.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: