[matplotlib-devel] html5/canvas interactive backend

A few weeks ago, Fernando pointed out the new canvas backend to gnuplot: http://skuld.bmsc.washington.edu/~merritt/gnuplot/canvas_demos/ See also: http://www.nabble.com/New-terminal-driver%3Aset-term-canvas-tc21364389.html Is there anyone that has worked on anything similar in matplotlib, i.

[matplotlib-devel] Sage patches to matplotlib

Here are a few patches that we in Sage have been applying to our version of matplotlib. I'm wondering if some or all of these might be incorporated into matplotlib, or if not, if you could comment on these patches. I've updated the following diffs to be against 0.99.0. I've separated the pat

Re: [matplotlib-devel] Sage patches to matplotlib

John Hunter wrote: > On Sun, Aug 9, 2009 at 7:48 PM, Eric Firing wrote: > > >> I did not commit #3. Apart from my lack of c++ expertise, I don't know how >> to implement it so that it takes effect only in the Solaris case. Therefore >> I am leaving this for John; or maybe he will pass it to Mik

[matplotlib-devel] not clipping objects in a plot

On this thread: http://www.mail-archive.com/matplotlib-devel@lists.sourceforge.net/msg05383.html clip_on was a suggested way of getting around the clipping that happens at the edge of a frame. In the Sage project, we are always setting the limits on the axes via set_xlim and set_ylim. Is the

[matplotlib-devel] axes.get_xticklines() minor parameter

I just noticed that the following two functions seem inconsistent: axes.get_xticklabels has a "minor" argument, which defaults to False However, axes.get_xticklines has no such argument, so in order to get the minor ticklines, one has to go down to the axes.xaxis object. This isn't a huge prob

[matplotlib-devel] transAxis attribute of the Axis object

In the documentation for the Axis object, I see that there is supposed to be a transAxis attribute. However, when grepping for it in the source, the only place it appears is in the documentation: gr...@tiny:~/sage/local/lib/python2.6/site-packages/matplotlib$ grep -r transAxis * axis.py:*

Re: [matplotlib-devel] not clipping objects in a plot

Andrew Straw wrote: > jason-s...@creativetrax.com wrote: > >> On this thread: >> >> http://www.mail-archive.com/matplotlib-devel@lists.sourceforge.net/msg05383.html >> >> clip_on was a suggested way of getting around the clipping that happens >> at the edge of a frame. In the Sage project, we

[matplotlib-devel] browse svn link on home page

Is there any chance someone could add a brief reference and link to the online svn repository somewhere on the front page of matplotlib? Maybe in the sidebar under "Need help?": For details on what's new, see the detailed changelog **or bro

[matplotlib-devel] spines with 'axes' positions show in wrong place?

Do the right and top spines display correctly when the position is set using 'axes' coordinates? import matplotlib.pyplot as plt import numpy as np fig = plt.figure() x = np.linspace(0,2*np.pi,100) y = 2*np.sin(x) ax = fig.add_subplot(1,1,1) ax.set_title('centered spines') ax.plot(x,y) ax.spines[

[matplotlib-devel] Automatically make room for tick labels FAQ entry

In the FAQ, there is an entry about adjusting subplot parameters to make room for really long tick labels: http://matplotlib.sourceforge.net/faq/howto_faq.html#automatically-make-room-for-tick-labels I made the example a little more general and included a utility function that takes care of ti

Re: [matplotlib-devel] spines with 'axes' positions show in wrong place?

Andrew Straw wrote: > jason-s...@creativetrax.com wrote: > >> Do the right and top spines display correctly when the position is set >> using 'axes' coordinates? >> >> > Jason, > > This looks like a bug. I'll look into it. Please ping me in a few days > if you haven't heard back. >

Re: [matplotlib-devel] spines with 'axes' positions show in wrong place?

John Hunter wrote: > On Thu, Sep 3, 2009 at 8:05 PM, wrote: > > >> This is just a friendly ping about the issue in this thread. I'm >> delaying the patch that shifts Sage's graphics to using the new >> matplotlib and spines, and I think resolving this issue would probably >> resolve the remain

[matplotlib-devel] 0.99.1 and the setup.cfg file

I just downloaded 0.99.1 and ran into some problems using it in Sage. Basically, in the tar.gz file, there was a setup.cfg file, which had the following: Note that some options are already uncommented, forcing a build of tkagg, wxagg, and macosx backends, and forcing the default backend to be

[matplotlib-devel] curved quiver arrows

How hard would it be to extend the quiver command to support curved arrows? For example, the U and V arrays, instead of giving just the vector, could for each vector give a list of x coordinates and a list of y coordinates for each segment of a vector. Additionally, C could give either a colo

Re: [matplotlib-devel] curved quiver arrows

Eric Firing wrote: > jason-s...@creativetrax.com wrote: >> How hard would it be to extend the quiver command to support curved >> arrows? For example, the U and V arrays, instead of giving just the >> vector, could for each vector give a list of x coordinates and a list >> of y coordinates for

Re: [matplotlib-devel] auto range limits for spines: please kick the tires

Andrew Straw wrote: Gary Ruben wrote: This looks nice Andrew, I haven't tried it, but I wonder whether it's possible to add a keyword arg to suppress the 0's at the origin which are cut through by the axes in the zeroed case (and/or possibly shift the 0 on the horizontal axis left). The sa

Re: [matplotlib-devel] Plots shifted up or to the left a pixel or so

On 6/11/10 9:44 AM, Michael Droettboom wrote: > On 06/11/2010 09:46 AM, Michael Droettboom wrote: > >> However, there's actually a bug in the quantizer that your example >> illustrates. Since the spine lines in your example have a stroke width >> of 4 pixels, they should actually be rounded to

Re: [matplotlib-devel] Plots shifted up or to the left a pixel or so

On 6/11/10 9:44 AM, Michael Droettboom wrote: > On 06/11/2010 09:46 AM, Michael Droettboom wrote: > >> However, there's actually a bug in the quantizer that your example >> illustrates. Since the spine lines in your example have a stroke width >> of 4 pixels, they should actually be rounded to

Re: [matplotlib-devel] Plots shifted up or to the left a pixel or so

On 6/11/10 1:02 PM, Michael Droettboom wrote: > >> It appears that the difficulty is that quantization is exposed at the >> python level only for collections, via iter_segments. >> >> > Sort of. Lines (but none of the other artists) follow what is set by > "set_snap" (the use of two terms fo

Re: [matplotlib-devel] Release schedule for version 1.0.1?

On 10/22/10 7:16 PM, Michael Droettboom wrote: >On 10/22/2010 05:45 PM, Russell E. Owen wrote: >> I'm curious when the next release of matplotlib is due. >> >> My application is suffering badly from the issue that an incorrect font >> cache will cause matplotlib to fail (the application mysteri