2010/1/3 Darren Dale <dsdal...@gmail.com>: > On Sun, Jan 3, 2010 at 9:11 AM, Pierre Raybaut <cont...@pythonxy.com> wrote: >> 2009/12/1 Darren Dale <dsdal...@gmail.com>: >>> On Tue, Apr 28, 2009 at 8:18 AM, Pierre Raybaut <cont...@pythonxy.com> >>> wrote: >>>> Hi all, >>>> >>>> I would like to contribute to matplotlib with this enhancement for the >>>> PyQt4 backend: the idea is to add a toolbar button to configure figure >>>> options (axes, curves, ...). >>>> >>>> It's based on a tiny module called formlayout to generate PyQt4 form >>>> dialog automatically. >>>> >>>> Some screenshots: >>>> http://code.google.com/p/formlayout/ >>>> >>>> So, if you're interested (all the following is GPL2): >>>> >>>> *matplotlib patch* >>> >>> Would you please submit an actual patch? I don't know exactly where >>> you intend these changes to be placed. >>> >>>> In FigureManagerQT.__init__, added: >>>> self.canvas.axes = self.canvas.figure.add_subplot(111) >>> >>> What is the purpose of this change? What if I didn't want such an axes >>> on my canvas? What if I want to layout my own axes([.2,.2,.75,.75]) or >>> add_subplot(311)? I don't think these changes can be accepted in the >>> current form, they don't appear to integrate well with the standard >>> behavior of the library. >>> >>> Darren >> >> Ok, I admit that it was very difficult to fix this -- it took me a lot >> of seconds without knowing very well matplotlib... ;-) > > [...] > >> Here is a zip file containing all you need (patch for backend_qt4.py, >> two scripts to be copied in backends/, and one .svg image to be copied >> to mpl-data/images/) > > [...] > > Your patch file is backwards, it would revert your changes if applied > to the updated code.
Sorry for this... I admit that I did this maybe too quickly. > It doesn't matter, the patch is so small that the > changes can just be cut and pasted. Unfortunately, however, I will not > have time to review your contribution closely enough to consider > committing it for at least two weeks, maybe more (conference and long > hours at work). I'll look into it when I get a chance, if someone else > doesn't beat me to it. > > Darren No problem, this is already part of Spyder's matplotlib patch for six months now, and I'm only using matplotlib through Spyder, so there is absolutely no hurry for me. Since the beginning I was just trying to be useful, to share something. I simply thought that this kind of feature was missing in matplotlib: matplotlib produces good looking figures but -compared to MATLAB- there is a serious lack of interactivity (and performance -- but matplotlib is at worst as slow as MATLAB, so it doesn't matter much). Pierre ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
