matplotlib-devel Mailing List for matplotlib

Just updated the MEP with more info. From what I gather, I don't see 
any problems. Refactoring WebAgg makes for slow progress, but nothing 
that breaks the main PR. As far as I can tell it can get merged while I 
work on the other backends and submit them as separate PRs. With this 
main branch merged we can then progress/finalise MEPs 22 and 23.
On 02/03/15 20:20, OceanWolf wrote:
> Hi everyone,
> Over the past week or so I have been working on what I now dub MEP27
> <https://github.com/matplotlib/matplotlib/wiki/MEP27> . I have already
> gotten quite far with it, but as I do some hefty changes (no breakages, and
> virtually 100% backward compatible) I wanted to make sure I got some input
> before continuing. I have now gotten far enough to know that the base code
> should work without any more tweaking.
>
> Best,
> OceanWolf
>
>
>
> --
> View this message in context: http://matplotlib.1069221.n5.nabble.com/MEP-27-Backend-Refactor-Gcf-tp45032.html
> Sent from the matplotlib - devel mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

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 Barker - NOAA Federal <
chr...@no...> wrote:
> On Mar 13, 2015, at 12:50 PM, Cyrille Rossant <cyr...@gm...>
> 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 advantages you get by rendering on the
> GPU.
>
> And OpenGL only supports simple primitives -- so it's substantially
> more a pain to do something as sole as render a filled polygon, let
> alone a spline.
>
> And yes, back In the day, it was faster to render on the video card,
> but CPUs have gotten a lot faster, and memory busses not so much.
>
> But whatever, I think we all agree that pushing the transformations to
> the GPU is the big win.
>
> -CHB
>
> > in one
> > second, you can send hundreds of millions of points on a modern GPU.
> > However it would be a bit slow to send large amounts of data at every
> > frame.
> >
> > GPU-based transformations are extremely fast, and you have full
> > control on how they're implemented; in the end, it's just arbitrary C
> > code that runs on the GPU on a per-vertex or per-pixel basis.
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>