| |||||||||||||
Matplotlib 1.2.0 releasedMatplotlib 1.2.0 releasedPosted Nov 16, 2012 13:41 UTC (Fri) by debacle (subscriber, #7114)Parent article: Matplotlib 1.2.0 released
Very nice!
I wonder, whether there are news about:
- threadsafety (AFAIK, matplotlib used to have problems when used from multiple threads)
- HTML5 backend (there was some work, but I'm not sure whether it ever reached "production quality")
(Log in to post comments)
Matplotlib 1.2.0 released Posted Nov 23, 2012 13:20 UTC (Fri) by njs (guest, #40338) [Link]
My understanding is that the original HTML5 backend turns out not to be maintainable. (It was basically based on porting matplotlib's internals to javascript, a classic boil-the-ocean sort of project.) The new idea is to do all the rendering on the server, and send bitmaps to the browser as needed for interactivity, like VNC. This seems much more plausible to me: http://mdboom.github.com/blog/2012/10/11/matplotlib-in-th...
Matplotlib 1.2.0 released Posted Nov 23, 2012 16:34 UTC (Fri) by debacle (subscriber, #7114) [Link]
Interesting approach. Let's see where it gets.
Michael is probably right, that moving huge amounts of data to the browsers JavaScript interpreter can be a problem. OTOH, letting the browser do the work scales nicely with the number of users, as the server does only have to provide more data, but not do more rendering work. Also, some interactive actions, like switching the visibility or colour of plot lines is sth. browsers can do nicely without any interaction with the server.
That's why we think about re-implementing parts of our matplotlib rendering in JavaScript, e.g. using D3 (https://github.com/mbostock/d3/wiki/Gallery), except for printing.
|
|||||||||||||