Re: [matplotlib-devel] Kivy backend

2015-03-13 Thread Cyrille Rossant
> Note that with OPenGL in general, its the transforming that buys you > performance -- when you push brand new data to be rendered, it takes a lot > of time to push that data to the video card, so drawing the first time > doesn't buy you much. But if you need to re-render that same data in a > dif

Re: [matplotlib-devel] Kivy backend

2015-03-13 Thread Ryan May
On Fri, Mar 13, 2015 at 12:53 PM, Chris Barker wrote: > On Fri, Mar 13, 2015 at 10:21 AM, Benjamin Root wrote: > >> Probably what I am most interested in from OpenGL is its transforms >> stack. >> > > OpenGL can't do anything with transforms that you couldn't do in python > (or C, or Cython). W

Re: [matplotlib-devel] Kivy backend

2015-03-13 Thread Chris Barker
On Fri, Mar 13, 2015 at 10:21 AM, Benjamin Root wrote: > Probably what I am most interested in from OpenGL is its transforms stack. > OpenGL can't do anything with transforms that you couldn't do in python (or C, or Cython). What it can do is push the transform computations to the GPU(s) -- mak

Re: [matplotlib-devel] Fwd: SciPy 2015 CFP Email 2

2015-03-13 Thread Olga Botvinnik
I'd be very interested in hearing a "state of matplotlib" talk. On Fri, Mar 13, 2015, 11:29 Phil Elson wrote: > Orchestrating MPL tutorials and talks in this thread would be a good idea. > I'd be happy to help anybody planning on submitting anything relating > specifically to matplotlib, and won

Re: [matplotlib-devel] Fwd: SciPy 2015 CFP Email 2

2015-03-13 Thread Phil Elson
Orchestrating MPL tutorials and talks in this thread would be a good idea. I'd be happy to help anybody planning on submitting anything relating specifically to matplotlib, and wonder if we should do a "state of matplotlib" type talk similar to the one Mike did 2 years ago. On 13 March 2015 at 02:

[matplotlib-devel] [ANN] Cartopy v0.12 release candidate

2015-03-13 Thread Phil Elson
I'm pleased to announce that cartopy v0.12.0rc1 has been tagged. This release has focused on improving the geometry projection stability, improving interfaces for data ingestion, rounding off Python 3 support, and generally improving the breadth of the gallery. A full overview of what's new in thi

Re: [matplotlib-devel] Kivy backend

2015-03-13 Thread Nicolas P. Rougier
By speed I meant to be able to render "big" plot (like a million point scatter plot or having 10 000 isolines, etc.) Concerning output quality, I think we're almost done. We have antialiases lines, markers and polygons (equivalent to agg), 2D agg-quality text (same techniques) and 3D decent te

Re: [matplotlib-devel] Kivy backend

2015-03-13 Thread Cyrille Rossant
2015-03-13 18:21 GMT+01:00 Benjamin Root : > Quite honestly, I am not all that concerned about speed (at least, I am > not talking about achieving gaming level performance). I am most concerned > about compatibility, quality of the image rendering, quality of the text > rendering, and consistency

Re: [matplotlib-devel] Kivy backend

2015-03-13 Thread Benjamin Root
Quite honestly, I am not all that concerned about speed (at least, I am not talking about achieving gaming level performance). I am most concerned about compatibility, quality of the image rendering, quality of the text rendering, and consistency across platforms. Probably what I am most interested

Re: [matplotlib-devel] Kivy backend

2015-03-13 Thread Thomas Caswell
MEP 25 is working towards providing a way to serialize the contents of a figure in a more controlled way. The main target of this is saving/reopening figures and export to bokeh/plotly/d3, but I think this would also work well for exporting everything off to an opengl backend. Tom On Fri, Mar 13

Re: [matplotlib-devel] Kivy backend

2015-03-13 Thread Nicolas P. Rougier
It might be difficult to stick to matplotlib architecture and still benefit from OpenGL speed. There are a lot of GL techniques that speed up things a lot but are are not really compatible. For example, isolines, quiver plots, image interpolations and most transformations can be handled direct

Re: [matplotlib-devel] Kivy backend

2015-03-13 Thread Cyrille Rossant
I don't think it would work like the other backends. Last time I checked, the MPL backend system would not let us achieve high performance. Currently we use Jake Vanderplas' mplexporter system that was developed for mpld3. Eventually, I guess we could expose the same interface as mpld3, i.e. repla

Re: [matplotlib-devel] Kivy backend

2015-03-13 Thread Benjamin Root
+1 on an OpenGL backend! Especially if I can off-load a lot of mplot3d stuff to it! Does vispy have any plans to eventually bring that into mainline matplotlib, or does it break too much with the standard set of backends to make sense in matplotlib (or maybe it is too much of a maintenance/packagin

Re: [matplotlib-devel] Kivy backend

2015-03-13 Thread Cyrille Rossant
> > Kivy is all built on OpenGL, so it would probably be pretty > straightforward to generate teh image with AGG, then dump it to the screen > as an OpenGL texture. But it would be a bit sad to not take advantage of > OpenGL at all in that process. (and getting AGG to work with Kivy may be > less t

Re: [matplotlib-devel] Kivy backend

2015-03-13 Thread Chris Barker
On Sat, Mar 7, 2015 at 4:17 PM, Thomas Caswell wrote: > Thank your for your interest, mpl on touch devices sounds super cool! > Indeed! > The easiest course is probably to develop a backend modeled after the > {qt,wx,gtk}Agg backends which embed an Agg backend into the gui framework > of choic