Ludovic Courtès <l...@gnu.org> writes: >> So, lots of things that a dedicated hacker could implement :) > > Is it a lot of work with d3 to switch to these other representations?
Each visualisation would probably require its own script (about as long as graph.js for the chord diagram) because the data may need to be prepared and mapped to SVG nodes differently. Switching within the same HTML document doesn’t make much sense because almost none of the SVG elements can be reused. The data structure I’m building up with the emit-* procedures should be reusable, though. (This isn’t very pretty because I’m emitting code to produce the data structure; it’s not a simple JSON description of the graph.) >> Does this mean that the generated HTML document would have to be a gexp >> referencing the file in the store? (I’m not sure how to implement >> this, but with a pointer or two I could give it a try anyway.) > > Yes, the HTML document would be generated in the store, […] Hmm, so each time I run “guix graph” the resulting HTML document ends up in the store. I was hoping to avoid this, actually, but since the HTML file is pretty small (when d3.js is not embedded) I guess it’s fine. ~~ Ricardo
