From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: d3js chord diagrams
Date: Tue, 25 Oct 2016 18:29:05 +0200 [thread overview]
Message-ID: <87bmy8z92m.fsf@gnu.org> (raw)
In-Reply-To: <87k2cwh7nm.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 25 Oct 2016 15:37:01 +0200")
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
[...]
>>> 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.
Well I realized that graph backends are expected to emit their output to
a port, so the HTML file would have to be written to that port anyway.
Ludo’.
next prev parent reply other threads:[~2016-10-25 16:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 22:09 d3js chord diagrams Ricardo Wurmus
2016-10-22 10:37 ` Alex Sassmannshausen
2016-10-22 17:42 ` Pjotr Prins
2016-10-25 9:01 ` Ludovic Courtès
2016-10-25 10:46 ` Ricardo Wurmus
2016-10-25 12:52 ` Ludovic Courtès
2016-10-25 13:37 ` Ricardo Wurmus
2016-10-25 16:29 ` Ludovic Courtès [this message]
2016-12-11 11:37 ` Ludovic Courtès
2016-12-11 15:24 ` Ricardo Wurmus
2016-12-11 19:51 ` Ricardo Wurmus
2016-12-11 22:59 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bmy8z92m.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).