On Sat, Mar 20, 2010 at 5:05 AM, Fernando Perez <fperez....@gmail.com> wrote:
> I wonder if it's possible to put things like a draw_if_interactive()
> call at the end of the OO methods... I realize that pyplot was the
> only one meant to do that, but if we are to encourage using the OO api
> more, then it's going to have to be as pleasant to use as pyplot... I
> don't know the codebase well enough to mess with this right now, so I
> hope someone who's more versed in that part of the code can make a fix
> for this whose impact isn't too severe on the runtime of OO code.
I'm not very inclined to this but I'll wait to hear what others think.
I use oo api in the interactive mode but I still prefer to call draw()
explicitly.
Of course, we can make it optional.
By the way, given that we now have "suplots" in the pyplot namespace,
can we have sca also?
For example,
# Two subplots, the axes array is 1-d
f, axarr = subplots(2, sharex=True)
sca(axarr[0])
plot(x, y)
title('Sharing X axis')
sca(axarr[1])
scatter(x, y)
Or, how about we make axes an context manager.
# Two subplots, the axes array is 1-d
f, axarr = subplots(2, sharex=True)
with axarr[0]:
plot(x, y)
title('Sharing X axis')
with axarr[1]:
scatter(x, y)
This may not very useful in the interactive mode, but may make a
script (written in pylab mode) more readable.
Regards,
-JJ
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
