Re: [matplotlib-devel] Kivy backend

2015-03-24 Thread Achyut Rastogi
No, sorry that was probably a mistake on my part, I thought that I would find the list of backends in __init__.py instead of https://github.com/rastogiachyut/matplotlib/blob/master/lib/matplotlib/rcsetup.py#L31 On Tue, Mar 24, 2015 at 10:45 PM, Michael Droettboom wrote: > Giving it a cursory gl

Re: [matplotlib-devel] Kivy backend

2015-03-24 Thread Michael Droettboom
Giving it a cursory glance, I think it's mostly current. Is there something specific that isn't working for you? Mike On 03/23/2015 08:09 AM, Achyut Rastogi wrote: Hello, I am having trouble following the instructions given here --> https://github.com/matplotlib/matplotlib/blob/master/lib/ma

Re: [matplotlib-devel] Kivy backend

2015-03-23 Thread Achyut Rastogi
Hello, I am having trouble following the instructions given here --> https://github.com/matplotlib/matplotlib/blob/master/lib/matplotlib/backends/backend_template.py#L16 it feels like the code was refractored (changed?) and those instructions never updated? On Sun, Mar 15, 2015 at 6:23 AM, Chris B

Re: [matplotlib-devel] Kivy backend

2015-03-14 Thread Chris Barker - NOAA Federal
On Mar 13, 2015, at 12:50 PM, Cyrille Rossant wrote: > Exactly. Note that pushing data on the GPU is not that slow: No -- and something has to be pushed to the video card at some point anyway. But my experience is that if you need to push the data to the CPU, that pretty much overwhelms the adv

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] 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

Re: [matplotlib-devel] Kivy backend

2015-03-10 Thread Achyut Rastogi
Thanks OceanWolf On Tue, Mar 10, 2015 at 3:13 PM, OceanWolf wrote: > One thing to note, that the backend structure will hopefully change soon > with a huge refactor of the backends. > > Take a look https://github.com/matplotlib/matplotlib/pull/4143 for the > current progress and feel free to giv

Re: [matplotlib-devel] Kivy backend

2015-03-10 Thread OceanWolf
One thing to note, that the backend structure will hopefully change soon with a huge refactor of the backends. Take a look https://github.com/matplotlib/matplotlib/pull/4143 for the current progress and feel free to give your comments. As a status update, I currently work on the WebAgg backend

Re: [matplotlib-devel] Kivy backend

2015-03-08 Thread Benjamin Root
Achyut, As I am sure everyone else on this list is sick of hearing, I have a book that will be coming out soon that can help explain many of your questions. It has a chapter explaining some of the differences between the interactive backends and how backends work, in general. The book is in the pr

Re: [matplotlib-devel] Kivy backend

2015-03-07 Thread Achyut Rastogi
Thank you Tom I read the qt backend and the first comment said about rendering from qt to agg, thank for the explaination, so if I don't understand some parts of the backend is this where I ask. On 5:47AM, Sun, Mar 8, 2015 Thomas Caswell wrote: > Achyut, > > Thank your for your interest, mpl on

Re: [matplotlib-devel] Kivy backend

2015-03-07 Thread Thomas Caswell
Achyut, Thank your for your interest, mpl on touch devices sounds super cool! 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 choice. In those cases we rely on Agg to handle the mpl specific drawin

[matplotlib-devel] Kivy backend

2015-03-07 Thread Achyut Rastogi
Hello , I am a novice gsoc aspirant and I want to write a backend for kivy, I read some of the other conversations on the mailing list and I know about the template you guys provide but I am having trouble getting started, can you please help me get up-to speed. I would be great help if you could t