Removing the legacy canvas cannot be done until there is an acceptable solution for users who do not have usable opengl on their systems. The Cairo canvas is not usable even on the fastest system I've have access to. Until either Cairo gets a significant speed boost, opengl becomes usable on all platforms, or we port wxDC to GAL, it will have to stay.
On 5/3/2016 6:51 PM, José Ignacio wrote: > What about simply removing the legacy canvas preemptively from the > development branch? gal-only is pretty usable by now and it might > reduce development workload for new features. > > On Tue, May 3, 2016 at 7:52 AM, Wayne Stambaugh <[email protected]> wrote: >> On 5/2/2016 4:54 PM, Chris Pavlina wrote: >>> I'd like to start having a look at how I can organize the preferences for >>> pcbnew, having mostly finished in eeschema. (A few things remain to be >>> tweaked >>> and will probably be done at the same time as pcbnew, to keep things in >>> sync). >>> >>> The problem of legacy preferences vs GAL preferences needs to be addressed. >>> How >>> do we want to handle that? At this point, I'm not sure what the timeline is >>> for >>> actual removal of legacy - should I wait until we do that? >> >> This is most likely going to be a while so you wont be able to remove >> the legacy canvas settings until we completely remove the legacy canvas >> from the source. >> >>> >>> If not, I want to try to merge options as much as possible. There are some >>> things that are duplicated between the two, which I'd like to fix. But the >>> bigger question is: how should we present to the user things that are only >>> available in one or the other? >>> >>> I could simply make sections on the preferences pages: "Legacy canvas only", >>> "OpenGL or Cairo canvas only". That's ugly and makes me cringe, but I can't >>> think of anything better. Two separate, parallel preferences systems like we >>> have right now just won't do. Thoughts? >> >> Even though separating the settings is probably going to be ugly, it's >> the most prudent way to go in terms of effort. If they are organized >> this way, it should be fairly easy to remove them when we finally get >> around to dumping the legacy canvas. >> >>> >>> _______________________________________________ >>> 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 _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
