matplotlib-devel Mailing List for matplotlib

Howdy,
in trying to teach a more structured use of mpl, I keep getting
annoyed by the whole figure(), add_subplot(), grab axes dance. I've
also seen students get confused by it. Does something along these
lines sound useful to have in the core (see attached)?
In use, below. You'd normally capture f, a = figaxes(...) to get the
figure and axes list, but I leave it off here for display purposes:
In [37]: figaxes()
Out[37]:
(<matplotlib.figure.Figure object at 0xa24b4cc>,
 [<matplotlib.axes.AxesSubplot object at 0x9e74a4c>])
In [38]: figaxes((2,1))
Out[38]:
(<matplotlib.figure.Figure object at 0xa359fcc>,
 [<matplotlib.axes.AxesSubplot object at 0xa47c66c>,
 <matplotlib.axes.AxesSubplot object at 0xa4a5c8c>])
In [39]: figaxes((2,2),dict(polar=True))
Out[39]:
(<matplotlib.figure.Figure object at 0xa6e340c>,
 [<matplotlib.axes.PolarAxesSubplot object at 0xa6fd5ac>,
 <matplotlib.axes.PolarAxesSubplot object at 0xa8b73cc>,
 <matplotlib.axes.PolarAxesSubplot object at 0xa8dd54c>,
 <matplotlib.axes.PolarAxesSubplot object at 0xa9686cc>])
Feedback welcome.
Cheers,
f

On Sat, Feb 13, 2010 at 2:23 PM, T J <tj...@gm...> wrote:
> Subclasses of Axes, such as PolarAxes, inherit many functions which
> make implicit assumptions of rectilinear coordinates. From a design
> perspective, it seems like most of these functions should not belong
> to the parent class, and that, perhaps, there should exist a
> RectilinearAxes(Axes) class. Essentially, Axes should contain only
> the methods that are generic enough for every type of axis. If I were
> to create my own subclass of Axes, I'll either have to tell people to
> not use some of the methods or I'll have to re-implement them all
> (which is definitely not going to happen quickly).
>
> Does this refactoring seem reasonable?
In general, I think this is reasonable thing to do.
However, I'm afraid that this refactoring will involve significant
efforts as the current Axes implementation implicitly assumes
rectlinear coordinates in so many places.
So, I'm not sure if any of the developers is willing to dive in, but
any contribution will be welcomed.
Regards,
-JJ
>
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

On Tue, Feb 16, 2010 at 3:51 AM, Philipp Bender <li...@ro...> wrote:
> Hi,
>
> because Wayne Watson complained in -users repeatedly about spelling errors
> without fixing or really pointing us to them I tried to find some in the
> chapter he mentioned and fixed them. Because I am not a native speaker I hope
> I did not "correct" already correct things.
>
> I attached the diff file.
>
> Please watch it _only_ if you have the time left, it's *really* no big thing.
Thanks Phillip for taking the time to convert this doc bug report from
the users list into a proper patch. Many of the
usages of axes that Wayne flagged as incorrect in his original report
are actually correct, so some of the patch is not correct but I
understand you were just converting his report into a usable patch.
But there were a couple of fixes in the patch that were worth applying
so I made these in svn HEAD.
> PS: Sphinx is great, good decision!
Yes, it's been great. We've developed a number of extensions, notably
the ipython and plot directives, that make writing documentation very
natural and easy, and overall I've been very happy with sphinx.