{"id":4209,"date":"2016-03-27T22:30:33","date_gmt":"2016-03-28T03:30:33","guid":{"rendered":"http:\/\/rud.is\/b\/?p=4209"},"modified":"2018-03-07T16:42:45","modified_gmt":"2018-03-07T21:42:45","slug":"nuclear-animations-in-d3","status":"publish","type":"post","link":"https:\/\/rud.is\/b\/2016\/03\/27\/nuclear-animations-in-d3\/","title":{"rendered":"Nuclear Animations in D3"},"content":{"rendered":"

As I said, I’m kinda obsessed with the “nuclear” data set. So much so that I made a D3 version<\/a> that’s similar to the R version I made the other day. I tried not to code much today (too much Easter fun going on), so I left off the size & color legends, but it drops the bombs and fills the radiation meters<\/strike> bars as each year progresses.<\/p>\n

Working in raw D3 reminds me how nice it is to work in R. Much cruft is abstracted away and the “API” in R (at least list ops and ggplot2) seem more consistent or at least less verbose.<\/p>\n

One big annoyance (besides tweaking projection settings) is that I had to set:<\/p>\n

script-src 'self' 'unsafe-eval';<\/pre>\n
on the [content security policy](http:\/\/content-security-policy.com\/) since D3 uses “eval” a bit. <\/p>\n
It’s embedded below and you can bust the frame via [this link](\/projects\/nucleard3\/index.html). I made no effort to have it fit on tiny screens (it just requires fidgeting with the heights\/widths of things), but it’s pretty complete code (including browser\/touch icons, content security policy & open graph tags) and it’s annotated to help R folks map between ggplot2 and D3. If you build anything on it, drop a note in the comments.<\/p>\n

\n