On Thu, May 12, 2011 at 2:59 AM, Benjamin Root <ben.r...@ou.edu> wrote: > Most things, we do know the sizes of. It is my understanding that it is the > text objects that is the unknown. If this could be solved, then a layout > engine would be much more feasible.
I doubt it. As far as I know, the main reason that things needed to be drawn is because the location and size of some artist depends on location and size of other artists. Unfortunately, with current matplotlib code, most of these things are determined inside the "draw" method. Therefore, we need to separate out those things out from the draw method. Another option, which I think is more feasible, is to implement a BBoxRenderer which does not draw anything but only update the size and location of artists. Regards, -JJ > The problem is that even LaTeX has to > re-render things multiple times to get this right for an arbitrary font. If > we were to restrict ourselves to particular fonts and package those fonts > with matplotlib, then we could have an internal table of size information > for each glyph and compute it on the fly and lay everything out right. But, > that would cause us to give up significant benefits for another benefit. ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
