On Thu, Oct 14, 2010 at 11:55 AM, Michael Droettboom wrote:
>
> I would suggest:
>
> canvas.print_figure(string_io, format='svg')
>
Fantastic! You now have your first commit in the IPython repo:
http://github.com/ipython/ipython/commit/4abff4a2c1b60b9cf342ce66bfe5113123e29294
Many thanks! Be
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 priv
On Thu, Oct 14, 2010 at 8:15 AM, Michael Droettboom wrote:
> 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
On Thu, Oct 14, 2010 at 7:51 AM, Fernando Perez 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 UCSF, and he embeds
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 fis
On Thu, Oct 14, 2010 at 10:05 AM, Robert Kern 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 mean that in o
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 mean that in order to support panning and zooming, we would need
> to keep an orig
On Thu, Oct 14, 2010 at 6:04 AM, John Hunter wrote:
> I believe the motivation here is in the separation of the ipython
> kernel process from the shell process, eg so the kernel can be running
> remotely and they can ship the image files across the wire. Fernando
> can clarify though.
Indeed.
On Thu, Oct 14, 2010 at 1:55 AM, Hans Meine wrote:
> Inkscape is an incredible piece of software, but maybe you should better test
> with e.g. Firefox, since there are *many* SVGs out there which only display
> fine in the almighty Inkscape. (Could you attach the example SVG? It looks
> simple e
On Thu, Oct 14, 2010 at 7:49 AM, Michael Droettboom 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 -- though th
On Thu, Oct 14, 2010 at 7:49 AM, Michael Droettboom 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 process from the sh
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 -- though those things are probably easier to workaround if
necessary.
So, it's n
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
> rende
13 matches
Mail list logo
