[matplotlib-devel] John: Thoughts on a standard test system

2008-12-22 Thread Drain, Theodore R
John, Sometime in January, we are going to spend some time fixing a few minor MPL bugs we've hit and a probably work on a few enhancements (I'll send you a list in Jan before we start anything - it's nothing major). We're also going to work on writing a set of tests that try various plots w/ un

Re: [matplotlib-devel] Native backend for Mac OS X

2008-12-22 Thread Michiel de Hoon
> Could you post the script you are using to do the > profiling? This is the code that I was using from pylab import * import numpy figure() x=numpy.arange(20) y=1+x**2 n = 4 for i in range(n*n): subplot(n,n,i+1) bar(x,y,log=True) xlim(-5,25) ylim(1,1e4) > The call to subplot/

Re: [matplotlib-devel] Native backend for Mac OS X

2008-12-22 Thread Michiel de Hoon
> The interactive backends (wx, tk, gtk) all handle draw_idle > in a way which delays the drawing until there are no > more commands to run. > > By changing draw_if_interactive to use draw_idle instead of > draw, > wouldn't this automatically smooth over the performance > issues without > the user

Re: [matplotlib-devel] Native backend for Mac OS X

2008-12-22 Thread John Hunter
On Fri, Dec 19, 2008 at 9:07 AM, Paul Kienzle wrote: >> Interactive is not the best word, but it is the rc parameter meaning >> "you are using mpl from the interactive prompt and want every pyplot >> command to update the plot". If the macosx backend is not doing this >> it should. If tkagg is