It is a new(ish) decision. Cairo is an implementation that doesn't require hardware features, but it is uselessly slow - even on my main build machine which is quite snappy I'd completely refuse to work under it. We need a GAL backend that works with minimal hardware at a usable speed, and I guess wxDC is supposed to be that.
On Fri, Jan 15, 2016 at 08:44:35PM +0100, "Torsten Hüter" wrote: > Hi, > > >>>> Are we even still going to have legacy pcbnew at the next release? > >>>> What's the schedule for fully deprecating it? > >> > >>It will not be deprecated until we have one for one feature parity > >>between the canvases and we can get by without it on all supported > >>platforms. AFAIK, Tom is working on a wxDC gal implementation which > >>should eliminate the second part. If this happens before the next > >>release, then there is no reason to continue to support the legacy canvas. > > Is this a new decision? I thought that wxDC is not that much interesting, > because it uses deprecated functions and is problematic on some platforms. > > I did an wxDC implementation, this was my last work on the GAL and then Orson > continued it and he should know this implementation. > > You can find the code here: > http://bazaar.launchpad.net/~kicad-product-committers/kicad/kicad-gal/files/head:/gal/wxdc/ > > Funny that this is almost 4 years old :) > > That could be helpful for Tom. > > Thanks, > Torsten > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
