- Kalyn Nakano: http://kalynnakano.com
- Tim Van Damme (Dropbox): http://maxvoltar.com
- Allison House: http://allisonhouse.co
- Max Schoening (Heroku, CloudApp): https://twitter.com/mschoening
- Mike Bostock: http://bost.ocks.org/mike
- Jan Dvořák (Apiary): http://www.jdvorak.eu
- Adam Morse (Salesforce): http://mrmrs.cc
- Zeke Sikelianos (Heroku): http://zeke.sikelianos.com
- Julie Ann Horvath (Github): http://julieannhorvath.com
- Alice Lee: http://byalicelee.com
var countries_data = {"type":"FeatureCollection","features":[ | |
{"type":"Feature","geometry":{"type":"MultiPolygon","coordinates":[[[[74.92,37.24],[74.57,37.03],[72.56,36.82],[71.24,36.13],[71.65,35.42],[71.08,34.06],[69.91,34.04],[70.33,33.33],[69.51,33.03],[69.33,31.94],[66.72,31.21],[66.26,29.85],[62.48,29.41],[60.87,29.86],[61.85,31.02],[60.84,31.5],[60.58,33.07],[60.94,33.52],[60.51,34.14],[61.28,35.61],[62.72,35.25],[63.12,35.86],[64.5,36.28],[64.8,37.12],[66.54,37.37],[67.78,37.19],[69.32,37.12],[70.97,38.47],[71.59,37.9],[71.68,36.68],[73.31,37.46],[74.92,37.24]]]]},"properties":{"name":"Afghanistan"},"id":"AF"}, | |
{"type":"Feature","geometry":{"type":"MultiPolygon","coordinates":[[[[19.44,41.02],[19.37,41.85],[19.65,42.62],[20.07,42.56],[20.59,41.88],[20.82,40.91],[20.98,40.86],[20.01,39.69],[19.29,40.42],[19.44,41.02]]]]},"properties":{"name":"Albania"},"id":"AL"}, | |
{"type":"Feature","geometry":{"type":"MultiPolygon","coordinates":[[[[2.96,36.8],[8.62,36.94],[8.18,36.52],[8.25,34.64],[7.49,33.89],[9.06,3 |
<html> | |
<head> | |
<title>Following along with Ben Christensen's Animated Sparkline using SVG Path and d3.js</title> | |
<script src="http://mbostock.github.com/d3/d3.v2.js"></script> | |
<link rel="stylesheet" type="text/css" href="style.css"> | |
</head> | |
<body> | |
<p> | |
<div id="graph1" class="aGraph" style="width:300px; height:100px;"></div> | |
</p> |
These are the languages, frameworks, and tools I'm using in my day-to-day workflow, listed in no particular order. Items that make me go "Oh yeah!" or are my primary tools are marked in bold.
My end-to-end process is front-loaded with research, sketches, whiteboarding, and figuring out a product spec with everyone that's involved in a project. My philosophy is: Design is not solely about deliverables; it's about understanding. It's not about a particular tool or language; it's about communication. It's not about pixels; it's about providing capability. I don't spend a lot of time in any particular application at first. The hardest thing to do well is figuring out what it is you want to design.
<iframe width="400" height="400" src="https://rd.io/i/QV5UlDNlDTs/" frameborder="0"></iframe> |
helpful bait | |
modern dock | |
relaxed lock | |
tame room | |
super chin | |
successful deer | |
adorable game | |
fuzzy water | |
rich pail | |
warm horn |
Replace this with a one or two line description of what this PR is intended to do. If it's a new feature, say what it does. If it's a fix for something, say what it fixes (link to an issue if available).
This <adds>/<fixes>/<removes>
:
- Adds something.
- Fixes something.
- Refactors something.
- Nixes something.
What's left:
- Task.