On Tue, Jul 17, 2007 at 08:01:41AM -0400, Michael Droettboom wrote: > TraitsUI seems really cool, but there are a couple of reasons I think > that should probably be considered lower priority. For one, it would > need to be generalized and ported (backend-ed) for all of matplotlib's > many gui backends. Also, I wonder how it fits into matplotlib's > paradigm as somewhere in between interactive and noninteractive > plotting. You would almost certainly want to tweak traits with the UI > and then save that back out as Python code, but code generators almost > never generate code that a human being would want to edit.
I was only mentionning TraitsUI as an option when integrating matplotlib into something larger, as a plotting engine (think something like http://sourceforge.net/projects/qme-dev, for instance, or some domain specific application). Of course I also have in mind an IDE, written in WxPython (most probably using enthought's envisage framework), with Ipython1 as the commandline engine, and MPL as the plotting engine. So far this is pure sci-fi, because we don't have the resources to write it, but it is nice if pieces start falling together. Gaël ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
