From: Ken M. <mc...@ii...> - 2005-12-02 17:25:39
|
On 12/02/05 04:54, massimo sandal wrote: > Hey, I didn't want to start a flamewar on all this! It's not a flamewar! Matt and haven't began maligning each other's ancestry yet! :-) > I just want to understand the objectives of the three projects. > It is true in your opinion? I'd say you've got it right. >> I understand that for _you_ a library that wx-dresses >> matplotlib is OK, but why not try to have a good feature-rich plotting >> package for wxPython? > > I have only tried a little wxmpl, and still didn't try MPlot, but I was > wondering: can MPlot be rewritten using WxMpl? It certainly could. WxMpl could take care of the basic user interaction stuff (e.g. zooming), leaving MPlot to focus on plot editing features. > But it's true that there are situation in which you badly need something > like that. I think the "stack" solution can be an idea. I really like the idea of stacking the different levels of abstraction on top of each other. It would allow us to reduce code duplication without limiting what application developers can do with matplotlib. >> I'm also really very concerned about the priority given to pylab and >> ipython. > > I'm really concerned about it too. As a MPL newbie, I found it very > misleading. I haven't really given it much thought. Most people presumably use MPL from IPython or scripts via pylab, so focusing documentation efforts on it make sense. I think that getting a good OO API manual would really improve things for application developers, but might be hard to justify in the big-picture. Ken |