epubjs
Version:
Render ePub documents in the browser, across many devices
83 lines (82 loc) • 9.92 kB
HTML
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:pls="http://www.w3.org/2005/01/pronunciation-lexicon" xmlns:ssml="http://www.w3.org/2001/10/synthesis" xmlns:svg="http://www.w3.org/2000/svg"><head><title>Appendix A. Appendix: Further Study</title><link rel="stylesheet" type="text/css" href="core.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"/><link rel="up" href="index.html" title="Interactive Data Visualization for the Web"/><link rel="prev" href="ch13.html" title="Chapter 13. Exporting"/><link rel="next" href="ix01.html" title="Index"/></head><body><section class="appendix" title="Appendix A. Appendix: Further Study" epub:type="appendix" id="further_study"><div class="titlepage"><div><div><h2 class="title">Appendix A. Appendix: Further Study</h2></div></div></div><p>You are a trouper for making it this far. We’ve covered a lot of ground, and by now you have a decent handle on D3’s basic concepts and common techniques. If you’ve learned anything, I hope it’s that there are always several (or tens, or hundreds of) ways to accomplish the same task—that’s the joy of programming, right? I’ve presented the ways that, to me, are the simplest or most intuitive, and the least difficult to understand. But there are probably <span class="emphasis"><em>better</em></span> ways to do anything that you learned in this book, whether “better” means “more computationally efficient” or “makes more sense to you and your way of working.” I’m a fan of the latter definition. Programming is like solving a puzzle; it’s up to you to figure out how to tell the computer what to do what you want—using language that you, the human, can still understand.<a id="I_indexterm_id320103" class="indexterm"/></p><p>D3 is a powerful tool, and we’ve only scratched the surface. As you begin work on your own visualization projects, you’ll discover many additional helpful methods and sneaky shortcuts. There are lots of valuable bits that I didn’t cover here, such as D3’s built-in methods for working with date and time values, dynamically selecting and calculating colors, and painlessly manipulating arrays, for all your client-side data processing needs—just to name a few. There is a <span class="emphasis"><em>lot</em></span> to this tool. I’ve tried to introduce you to the core concepts, and now you’re ready to go dig into the pieces that really interest you.</p><p>So, where to turn next? Here’s a collection of valuable resources to aid you in your quest. Keep in mind that the D3 software itself is still evolving, and so are these resources. By the time you read this, there might be some other helpful website or set of tutorials not mentioned here. That is why I recommend that you don’t just read, but <span class="emphasis"><em>get involved</em></span> with the D3 community. Join <a class="ulink" href="https://groups.google.com/forum/#!forum/d3-js" target="_top">the Google Group</a>, follow people on Twitter, and keep your eyes open for the latest developments. Start a discussion, and meet fellow data visualizers in your local area. If there aren’t D3 datavis groups getting together in your area yet, then start one yourself. The more we can learn from each other, the better.</p><p>After all, having worked through this book, you’re part of the community now (whether you like it or not). Welcome!</p><div class="sect1" title="Books"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="_books">Books</h2></div></div></div><p><a class="ulink" href="http://shop.oreilly.com/product/0636920025429.do" target="_top"><span class="emphasis"><em>Getting Starting with D3</em></span></a> by Mike Dewar. O’Reilly, 2012.</p><p>Yes, there’s only one other book on D3 so far. Mike Dewar’s introduction tackles some more advanced topics, and includes sample projects with real-world data from New York City’s transportation system. (Fun!)</p></div><div class="sect1" title="Websites"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="_websites">Websites</h2></div></div></div><div class="variablelist"><dl><dt><span class="term">
<a class="ulink" href="http://d3js.org" target="_top">d3js.org</a>
</span></dt><dd>
Your starting point for everything D3.
</dd><dt><span class="term">
<a class="ulink" href="https://github.com/mbostock/d3/wiki/Gallery" target="_top">github.com/mbostock/d3/wiki/Gallery</a>
</span></dt><dd>
The D3 gallery contains <span class="emphasis"><em>hundreds</em></span> of examples. Add your own work!
</dd><dt><span class="term">
<a class="ulink" href="http://bl.ocks.org/mbostock" target="_top">bl.ocks.org/mbostock</a>
</span></dt><dd>
Even more examples, in this case all by Mike Bostock, each one typically highlighting just one of D3’s features.
</dd><dt><span class="term">
<a class="ulink" href="https://github.com/mbostock/d3/wiki/API-Reference" target="_top">github.com/mbostock/d3/wiki/API-Reference</a>
</span></dt><dd>
The D3 API reference, an essential reference for every method and its parameters.
</dd><dt><span class="term">
<a class="ulink" href="http://stackoverflow.com/questions/tagged/d3.js" target="_top">stackoverflow.com/questions/tagged/d3.js</a>
</span></dt><dd>
When you get stuck, post questions on StackOverflow with the <code class="literal">d3.js</code> tag.
</dd><dt><span class="term">
<a class="ulink" href="https://groups.google.com/forum/?fromgroups#!forum/d3-js" target="_top">groups.google.com/forum/?fromgroups#!forum/d3-js</a>
</span></dt><dd>
Everyone who’s anyone is on the D3 Google Group. Find out about the latest projects and developments here. (Please save technical questions for StackOverflow.)
</dd><dt><span class="term">
<a class="ulink" href="http://bl.ocks.org" target="_top">bl.ocks.org</a>
</span></dt><dd>
A service for posting code hosted on GitHub’s Gist, by Mike Bostock. Perfect for quickly sharing your work with others, such as when seeking help on StackOverflow or boasting about your latest triumph on the Google Group.
</dd><dt><span class="term">
<a class="ulink" href="http://blog.visual.ly/creating-animations-and-transitions-with-d3-js/" target="_top">blog.visual.ly/creating-animations-and-transitions-with-d3-js/</a>
</span></dt><dd>
An excellent tutorial on <span class="emphasis"><em>Creating Animations and Transitions With D3</em></span> with lots of inline, interactive examples by Jérôme Cukier.
</dd><dt><span class="term">
<a class="ulink" href="http://www.d3noob.org" target="_top">d3noob.org</a>
</span></dt><dd>
A new, promising resource for D3 tips and tricks.
</dd><dt><span class="term">
<a class="ulink" href="http://tributary.io" target="_top">tributary.io</a>
</span></dt><dd>
A live-coding environment for experimenting with D3 code, by Ian Johnson.
</dd><dt><span class="term">
<a class="ulink" href="https://github.com/d3/d3-plugins" target="_top">D3 Plug-ins</a>
</span></dt><dd>
A listing of all the official plug-ins that extend D3’s functionality, in case it doesn’t do enough for you already.
</dd></dl></div></div><div class="sect1" title="Twitterers"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="_twitterers">Twitterers</h2></div></div></div><p>Twitter is a great way to find out about the latest projects and D3 developments. At the risk of omitting many amazing people, here are some you should follow:</p><div class="variablelist"><dl><dt><span class="term">
<a class="ulink" href="https://twitter.com/mbostock" target="_top">@mbostock</a>
</span></dt><dd>
Mike Bostock, for announcements on D3’s progress as well as new visualizations for <span class="emphasis"><em>The New York Times</em></span>.
</dd><dt><span class="term">
<a class="ulink" href="https://twitter.com/jasondavies" target="_top">@jasondavies</a>
</span></dt><dd>
Jason Davies, for all manner of geographic and mathematical mapping experiments.
</dd><dt><span class="term">
<a class="ulink" href="https://twitter.com/d3visualization" target="_top">@d3visualization</a>
</span></dt><dd>
Christophe Viau, for frequent updates from all over the D3 universe.
</dd><dt><span class="term">
<a class="ulink" href="https://twitter.com/enjalot" target="_top">@enjalot</a>
</span></dt><dd>
Ian Johnson, for loads of new coding tools and techniques, plus video tutorials.
</dd><dt><span class="term">
<a class="ulink" href="https://twitter.com/syntagmatic" target="_top">@syntagmatic</a>
</span></dt><dd>
Kai Chang, for too many D3 experiments to count.
</dd><dt><span class="term">
<a class="ulink" href="https://twitter.com/jcukier" target="_top">@jcukier</a>
</span></dt><dd>
Jérôme Cukier, for innovative visualization projects with insightful process notes.
</dd><dt><span class="term">
<a class="ulink" href="https://twitter.com/darkgreener" target="_top">@darkgreener</a>
</span></dt><dd>
Anna Powell-Smith, for beautiful interactive visualizations that explore personally relevant data.
</dd><dt><span class="term">
<a class="ulink" href="https://twitter.com/vlandham" target="_top">@vlandham</a>
</span></dt><dd>
Jim Vallandingham, for excellent process notes on projects as well as great tutorials.
</dd><dt><span class="term">
<a class="ulink" href="https://twitter.com/alignedleft" target="_top">@alignedleft</a>
</span></dt><dd>
Scott Murray, for learning about errata, updates, and revisions to this book, as well as future data-driven projects.
</dd></dl></div><p>I should acknowledge that, yes, there are mostly men listed here. As of this writing, the community of D3 users and contributors tends to skew quite male. I hope that future editions of this book can confidently include a more diverse listing.</p></div></section></body></html>