mpl1 draft

> In matplotlib, the plot functions are matplotlib.axes.Axes methods and
> I think there is consensus that this is a poor design.

Well, the OO interface has always felt a bit clunky to me, but I'm not
sure where else plot functions could go -- I'd love to hear ideas, though.

With a few primitives (add_artist, set_property, get_property, x/y axis,
labels, grids), all of the plot types can be implemented identically
outside of the axes class. Most of them are implemented that way already,
and only need to change ax.plot to plot(self=ax). Default to gca() and
you have pylab.

> Also, everything should be numpy enabled,
> and the sequence-of-python-tuples approach that many of the
> collections take should be dropped.

who hoo!

However, numpy doesn't handle "ragged" arrays well. I wonder if there's
a good way to implement those, so that transforms can be done

Can you do it with simple vectors, and an index vector indicating where
the different objects start? The transformations can run simply
through the sets of indices without bothering about object boundaries.
The path objects can use vector slices, which IIRC, are simply views
into the vectors and don't require copying the data. It would be
easy enough to hide this in a class so that it acts like a sequence
of lines to the caller.

  - Paul


On Thu, Jul 19, 2007 at 03:31:26PM -0700, Christopher Barker wrote: