Hi,
Op den Dunnersdag 14 Oktober 2010 Klock 01:36:52 hett Fernando Perez schreven:
I've been investigating further the bug where clipped paths in SVG
render wrong in our console. It turns out the mpl team already fixed
some things on their side, and I can confirm that their SVGs now
render
On Thu, Oct 14, 2010 at 7:49 AM, Michael Droettboom md...@stsci.edu wrote:
I haven't had a chance to look at the new Qt shell in ipython yet -- but
is it necessary to go through a file? Perhaps writing a native Qt4
I believe the motivation here is in the separation of the ipython
kernel
On Thu, Oct 14, 2010 at 7:49 AM, Michael Droettboom md...@stsci.edu wrote:
It looks like the QtSvg module is targeting SVG Tiny 1.2, which does not
support clipping:
http://doc.qt.nokia.com/4.3/qtsvg.html
SVG Tiny also limits a lot of the CSS styling things that matplotlib
makes use of --
On Thu, Oct 14, 2010 at 10:05 AM, Robert Kern robert.k...@gmail.com wrote:
On 10/14/10 8:57 AM, Benjamin Root wrote:
My only concern about that approach -- if I understand it correctly -- is
that
this path clipping would have to be redone at every change in view
limits.
Wouldn't that
I'm not sure what's causing this. I don't have a Python = 2.6
environment with all the Qt bells and whistles to test ipython HEAD with
(our house standard here is still 2.5)... Once I find the time for
that, hopefully I can see what's going on. But I suspect paste() is
doing something fishy
On Thu, Oct 14, 2010 at 7:51 AM, Fernando Perez fperez@gmail.com wrote:
Well, the client can save a session to html, svgs and all:
http://fperez.org/tmp/ipython-svg.xml
If the svg has extra metadata embedded, this will preserve it. The
author of the html saving works in genomics at
Yeah -- the print_* format methods should probably be made private.
They don't properly save/restore state -- that is all done in one place
in the higher-level function print_figure.
I would suggest:
canvas.print_figure(string_io, format='svg')
I'll go ahead and make these functions