On 10/25/2013 06:42 PM, Todd wrote:
I think another problem is having pyplot and axes as dumping grounds for all plot types. This probably made sense back when there were only a few types of plots, but now there is a massive number of them. They all end up in one large class with one large documentation page, making it very hard to find exactly what you are looking for.

In order to make the plots really useful, I definitely think a reorganization is in order. I think matplotlib needs an general module, perhaps "plots", that contains sub-modules for different types of plots (like bar plots), and those sub-modules contain functions, all of which have an axes object as their first argument. These could still be attached to axes as methods at least as a transition, but it would leave the axes class with methods that really have to do with axes, and not plotting per se. This would also make it possible to put code shared between plot types with those plot types in their module.

Nelle Varaquoax has already started this work on master. The separation of core axes functionality from plotting functionality has already been done, and the next steps involve organizing the plotting functionality further. This is a gargantuan task, and I'm sure Nelle would appreciate some assistance if you wanted to coordinate with her.

Mike


On Thu, Oct 24, 2013 at 8:39 PM, Chris Barker <chris.bar...@noaa.gov <mailto:chris.bar...@noaa.gov>> wrote:

    On Thu, Oct 24, 2013 at 8:29 AM, Michael Droettboom
    <md...@stsci.edu <mailto:md...@stsci.edu>> wrote:
    > Here are the notes with action items from the meeting:

    thanks for posting that. I see:

    pylab - should it stay or should it go?

    Comment from the peanut gallery:

    Go.

    But beyond that, matplotlib.pyplot is a big mess of both the
    matlab-style state-machine current figure, current axis stuff, and
    what you need to do (at least reasonably on the command line) OO
    interface.

    This makes it really hard to teach to newbies -- I just did this last
    night, and made a point to use tutorials that emphasize the OO
    interface (Thanks Ben Root, Katy Huff, and Antony Scopatz, and I'm
    sure others that helped put the materials together that I stole
    from...). However, there were still a number of examples in there that
    just called "plot()" or whatever, and even if there were not, the
    namespace is really cluttered with stuff!

    Anyone like the idea of an matplotlib.ooplot namespace that would have
    just what you need to use the oo style?

    -Chris

    --

    Christopher Barker, Ph.D.
    Oceanographer

    Emergency Response Division
    NOAA/NOS/OR&R (206) 526-6959 <tel:%28206%29%20526-6959>   voice
    7600 Sand Point Way NE (206) 526-6329 <tel:%28206%29%20526-6329>   fax
Seattle, WA 98115 (206) 526-6317 <tel:%28206%29%20526-6317> main reception

    chris.bar...@noaa.gov <mailto:chris.bar...@noaa.gov>

    
------------------------------------------------------------------------------
    October Webinars: Code for Performance
    Free Intel webinars can help you accelerate application performance.
    Explore tips for MPI, OpenMP, advanced profiling, and more. Get
    the most from
    the latest Intel processors and coprocessors. See abstracts and
    register >
    http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
    _______________________________________________
    Matplotlib-devel mailing list
    Matplotlib-devel@lists.sourceforge.net
    <mailto:Matplotlib-devel@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/matplotlib-devel




------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk


_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


--
                   _
|\/|o _|_  _. _ | | \.__  __|__|_|_  _  _ ._ _
|  ||(_| |(_|(/_| |_/|(_)(/_|_ |_|_)(_)(_)| | |

http://www.droettboom.com

------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Reply via email to