Re: [matplotlib-devel] Planning for 1.3.0

2013-04-12 Thread Derek Homeier
On 11.04.2013, at 6:38PM, Michael Droettboom wrote: > Congrats to everyone on a successful 1.2.1 -- there was a relatively > small influx of bug reports following it -- perhaps a sign of improving > quality? Thanks and congratulations to everyone involved as well; I've built 1.2.1 on MacOS X

Re: [matplotlib-devel] Planning for 1.3.0

2013-04-12 Thread Michiel de Hoon
Hi Derek, The slow speed for long paths like the one in your example was due to a limitation to Quartz itself. This was solved by breaking the path up into subpaths of up to 100 points. But you mentioned that releases before 1.2 were not slow (and I verified this with matplotlib 1.1.1), suggest

[matplotlib-devel] interesting article about visualization

2013-04-12 Thread Michael Droettboom
http://blogs.hbr.org/cs/2013/04/the_science_of_what_we_do_and_dont_know_about_data_visualization.html -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform inc

[matplotlib-devel] Timers independent of canvases

2013-04-12 Thread Michiel de Hoon
Dear all, The animation code in matplotlib relies on timers to update the animated figures. Currently a new timer is created by calling new_timer on a canvas, as in >>> f = pylab.figure() >>> timer = f.canvas.new_timer() This seems a bit of a wrinkle. For example, you may want to associate a t