On Wed, Sep 22, 2010 at 2:28 PM, Christopher Barker
<chris.bar...@noaa.gov>wrote:
> Benjamin Root wrote:
> > On Wed, Sep 22, 2010 at 12:04 PM, Russell E. Owen <ro...@uw.edu
> > I'd be much happier with a
>
> > Ditto on this. In addition, it would be useful to prevent axes labels
> > from spilling over into another axes' area.
>
> Someone was working on a wxSizer-like layout tool for MPL -- anyone know
> what happened to that?
>
> Also -- do all MPL artists (text, etc) know enough about how big they
> are to do this at all? I recall trying to do a bit myself, and had a
> hard time finding out how big a label was, and thus didn't know where to
> put an axis so the label wouldn't be chopped off.
>
> -Chris
>
>
I think the issue was that it could not be generalized that an artist knows
its size until it comes time to render. I think the main culprit here is
text labels (particularly latex stuff). If it could be known what an
artist's size is when the artist is made, then I think a lot of code could
be simplified because all artists would reference itself relative to their
parent artist (think particularly how axes and figure objects have size
properties).
Although, as a counter-point, we don't want to inhibit a user's ability to
have something outside of its parents (annotations, arrows and such). Maybe
most artists would have a property indicating whether it should be
constrained or not.
Now that I think about it even more, doing a proper layout engine would be a
headache...
Ben Root
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
