On Jul 19, 2007, at 3:05 PM, Bill Baxter wrote: > Chaco may be formidable and complex, but so is the list of features > and requirements you just posted. What about just focusing on a Pylab > wrapper for Chaco? And working with Peter to make Chaco everything > you envison. Or does Chaco have the same needs-a-rewrite architecture > issues as the mpl?
There are certainly directions I'd like to take the architecture, but I'm not planning a rewrite anytime soon. One rewrite every 4 years is more than enough for me. ;) > Just to be clear, I don't have any first hand experience with Chaco, > other than running the demos once. The main problems with Chaco I'm > aware of are 1) entanglement with the rest of ETS, which they're > working on, 2) no pylab like easy-to-use interface. (1): Other than traits (and a teensy bit of traits UI), Chaco requires only Kiva and Enable. Its setup.py reflects this. This has been the case for a while, but historically the issue has been that all the interdependencies at the traits UI level sucked in basically the rest of ETS. (2): Chaco2.shell has some rudimentary pylab-like features, but obviously is nowhere near complete. There are some examples of the sorts of things it can do: https://svn.enthought.com/enthought/ browser/branches/enthought.chaco2_2.0/examples/shell. One thing to note about the shell is that its commands are just convenience functions that wrap existing Chaco containers and components, so the structure of the live plot that is built with, say, an imshow() command is similar to one that you could build by hand. This means that you can dynamically extend its behavior by adding new tools that the command-line interface doesn't know about. It also means that you can use the command-line interface to construct a plot (or grid of plots) and trivially embed that into an external application, no differently than if you had hand-coded to the lower, object-oriented layer. -Peter ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
