I've been hacking away at adding support for "dropped spines" to MPL (e.g. http://jeb.biologists.org/cgi/content/full/211/3/341/FIG7 ) and have come to the conclusion that there is a fundamental issue in the code base that the traits package has solved -- many values that depend on other values with complicated stuff that happens when one of the parent values changes. For example, the location of the text from the xaxis depends on the padding value in addition to the xaxis location. Now I'm trying to add another element to the mix -- namely an axis spine that can change location -- and things are going to spiral into a (further) collection of special-cased updates unless there's some reworking of the infrastructure.
So, the question is, should I attempt to use traits for this? I guess that I won't have the time to re-write the entire code base to use traits, but I'd like make a stab a stab at dropped spine support with the knowledge that, should I be successful, there's at least a chance we would again ship traits with MPL. I imagine we could incrementally move more and more to traits if I'm successful, particularly now that we have the beginnings of a unit test infrastructure (thanks James!). -Andrew ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
