Philippe Rivière

All options I can think of have drawbacks: - gist comments, but notifications are broken https://github.com/isaacs/github/issues/21 - d3's slack, but needs registration - gitter.im, but adds another channel - email,...

ha but there _is_ already a (well populated!) gitter d3 channel https://gitter.im/d3/d3 ; kinda solves it for me

And here's how it could look https://bl.ocks.org/Fil/e5b449606ca1e3e120cda8d08a7f3351

I can confirm that adding `allow-modals ` works, also if that is the choice (and I support it), it would be necessary to remove `alertOverride` in `public/js/utils/parseCode.js` See also #185.

The examples should be: - very well done (mbostock grade) - short - easy to understand - demonstrating one (only one) point of code or technique - visually nice -...

We can have: - the general update pattern https://bl.ocks.org/mbostock/a8a5baa4c4a470cda598 - transitions - d3.geo (lots!!) http://bl.ocks.org/Fil/48734366b4d64aa1b26bd256ee8f7c5e - customized forces - voronoi - colors

Not sure about the "random" part; I'd like to be able to find the same block that caught my attention when I arrived. So maybe an example of the day...

Wouldn't hurt, but I'm not sure it solves the problem in general. People will find and reuse a block by different means, and when they comment on it, the author...

the bad commit was 09f12f6e01d384832ce061051506c5c4bbee9a6f if you want to see the botched image it is at https://gist.githubusercontent.com/Fil/c6efde7d8271a8728cd23c0d268ea787/raw/09f12f6e01d384832ce061051506c5c4bbee9a6f/image.jpg https://gist.github.com/Fil/c6efde7d8271a8728cd23c0d268ea787/09f12f6e01d384832ce061051506c5c4bbee9a6f#file-image-jpg

Another solution is to save all scripts to localStorage before running the iframe: ``` diff --git a/public/js/components/renderer.js b/public/js/components/renderer.js index 23ba43d..49618d0 100644 --- a/public/js/components/renderer.js +++ b/public/js/components/renderer.js @@ -40,6 +40,21 @@ var...