Re: [matplotlib-devel] Bug when embedding Matplotlib 0.91.2 in PyQt 4.4.2

2008-05-31 Thread Darren Dale
Hi Pierre, On Friday 30 May 2008 5:21:01 pm Pierre Raybaut wrote: > First, I would like to congratulate you for your work on Matplotlib. I > am using Matplotlib widgets in all my current projects, embedded in PyQt > graphical user interfaces. > > As you may know, PyQt 4.4.2 has been released a few

Re: [matplotlib-devel] future of mpl documentation

2008-05-31 Thread Darren Dale
I'll be working on converting docstrings to rest this weekend. Should any of this be done on the branch? Or should we just focus on the trunk? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) V

Re: [matplotlib-devel] new release?

2008-05-31 Thread Charlie Moad
Sorry for the delay but I am running into windows/gtk problems. I am getting linking errors for "_gdk_draw_rgb_32_image" and two other gdk symbols. I can't seem to find which lib they are in either. I installed "gtk-dev-2.12.9-win32-2.exe". Do we target a specific version of gtk? I am thinking

Re: [matplotlib-devel] new release?

2008-05-31 Thread John Hunter
On Sat, May 31, 2008 at 9:47 AM, Charlie Moad <[EMAIL PROTECTED]> wrote: > Sorry for the delay but I am running into windows/gtk problems. I am > getting linking errors for "_gdk_draw_rgb_32_image" and two other gdk > symbols. I can't seem to find which lib they are in either. I > installed "gtk

Re: [matplotlib-devel] new release?

2008-05-31 Thread Charlie Moad
Rolling gtk and pygtk back to 2.10 worked. https://sourceforge.net/project/showfiles.php?group_id=80706 I may be a little rusty on the builds, so please give them a try before the announcement. - Charlie On Sat, May 31, 2008 at 12:31 PM, John Hunter <[EMAIL PROTECTED]> wrote: > On Sat, May 31,

Re: [matplotlib-devel] future of mpl documentation

2008-05-31 Thread John Hunter
On Sat, May 31, 2008 at 9:19 AM, Darren Dale <[EMAIL PROTECTED]> wrote: > I'll be working on converting docstrings to rest this weekend. Should any of > this be done on the branch? Or should we just focus on the trunk? As far as I am concerned, the documentation effort is for the trunk. The only r

Re: [matplotlib-devel] future of mpl documentation

2008-05-31 Thread Darren Dale
On Saturday 31 May 2008 12:36:11 pm John Hunter wrote: > On Sat, May 31, 2008 at 9:19 AM, Darren Dale <[EMAIL PROTECTED]> wrote: > > I'll be working on converting docstrings to rest this weekend. Should any > > of this be done on the branch? Or should we just focus on the trunk? > > As far as I am

Re: [matplotlib-devel] future of mpl documentation

2008-05-31 Thread Darren Dale
On Friday 23 May 2008 7:54:27 pm John Hunter wrote: > On Fri, May 23, 2008 at 6:14 PM, Darren Dale <[EMAIL PROTECTED]> > wrote > > > I have to break here for the weekend, I'll be back monday afternoon. > > Leave some for me! (although I'll owe doughnut to whoever can fix the > > arrow docstring). >

Re: [matplotlib-devel] future of mpl documentation

2008-05-31 Thread Darren Dale
On Saturday 31 May 2008 4:14:39 pm Darren Dale wrote: > On Saturday 31 May 2008 12:36:11 pm John Hunter wrote: > > On Sat, May 31, 2008 at 9:19 AM, Darren Dale <[EMAIL PROTECTED]> > > wrote: > > > I'll be working on converting docstrings to rest this weekend. Should > > > any of this be done on the

Re: [matplotlib-devel] future of mpl documentation

2008-05-31 Thread Fernando Perez
Hey folks, I'm super excited about this, so I decided to give it a quick test run with current trunk SVN. Running ./make.py in the doc/ directory worked for a while, and then stalled at: Sphinx v0.3, building latex trying to load pickled env... done building [latex]: all documents updating envi

Re: [matplotlib-devel] future of mpl documentation

2008-05-31 Thread John Hunter
On Mon, May 26, 2008 at 1:50 PM, Tony Yu <[EMAIL PROTECTED]> wrote: > I played around with the script, but in the process I ended up rewriting it > a bunch. I'm sure I've violated come coding guidelines along the way; my > apologies. And I made several changes -- mainly to simplify the logo. My

Re: [matplotlib-devel] future of mpl documentation

2008-05-31 Thread John Hunter
On Sat, May 31, 2008 at 3:19 PM, Darren Dale <[EMAIL PROTECTED]> wrote: Darren> I have to break here for the weekend, I'll be back monday afternoon. Darren> Leave some for me! (although I'll owe doughnut to whoever can fix the Darren> arrow docstring). John> I'll claim that doughnut. D

Re: [matplotlib-devel] future of mpl documentation

2008-05-31 Thread John Hunter
On Sat, May 31, 2008 at 9:01 PM, Fernando Perez <[EMAIL PROTECTED]> wrote: > I don't know if you are so in the middle of things that you'd rather > not get bug reports on this for a while. If that's the case I'll wait > until the dust settles a bit. Well, we definitely want our docs to build so

Re: [matplotlib-devel] future of mpl documentation

2008-05-31 Thread John Hunter
On Sat, May 31, 2008 at 7:50 PM, Darren Dale <[EMAIL PROTECTED]> wrote: > I just realized, though, that I should probably be striving to conform with > the standard that the numpy and scipy folks put together: > http://projects.scipy.org/scipy/numpy/wiki/CodingStyleGuidelines and > http://svn.scip

Re: [matplotlib-devel] future of mpl documentation

2008-05-31 Thread Darren Dale
On Saturday 31 May 2008 10:19:47 pm John Hunter wrote: > On Sat, May 31, 2008 at 9:01 PM, Fernando Perez <[EMAIL PROTECTED]> wrote: > > I don't know if you are so in the middle of things that you'd rather > > not get bug reports on this for a while. If that's the case I'll wait > > until the dust

Re: [matplotlib-devel] future of mpl documentation

2008-05-31 Thread Tony Yu
On May 31, 2008, at 10:30 PM, John Hunter wrote: > > And I made several changes -- mainly to simplify the logo. My wife > thought it looked busy, and she has better taste than I do, so I > stripped it down a bunch and added the many small subplots as a > sidebar on the right. I agree, the strip

Re: [matplotlib-devel] future of mpl documentation

2008-05-31 Thread John Hunter
On Sat, May 31, 2008 at 11:27 PM, Tony Yu <[EMAIL PROTECTED]> wrote: > I like the new color scheme on the website. Since you asked for criticism, > though, I'm not a fan of the blue "matplotlib" in the logo (on the website, > the attached logo is actually different). I think black or a dark gray l