I’d think the optimum long term solution would be something along the lines of generating a webp, png, or svg of the graph as part of the html delivery. That would remove the js bloat folder. (I don’t see any reason to have it generated on the fly each time with a now fixed set of data) Of course, that means some work, so it would be an enhancement and not much of a priority since it is easy enough to go the pdf route for now.
Regards, Adrien > On Dec 30, 2019 w1d364, at 9:37 AM, D via gnucash-user > <gnucash-user@gnucash.org> wrote: > > I may be a little slow here, but it seems to me this is something of an edge > case. Isn't this analogous to sending an html file without including embedded > images? Very efficient; not very informative. > > Finally, from my perspective, a 100kb pdf is not a huge payload to be > sending, but I understand your situation may be different. > > David T. > > On December 30, 2019, at 4:06 AM, boldstripe <michael.nab...@wengam.com> > wrote: > > Christopher: Thanks, I confirm your method of making a Firefox webpage > creates an HTML version that works across platforms, at least from Linux to > MacOS. > > This could be useful if you really want HTML, but Firefox stores the > javascript code in a folder that is 772 kB, compared to about 8 kB for the > platform-specific HTML and about 100 kB for a PDF. > > I will study how to contribute to documentation, thank you. _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
