I can imagine it, but I thought it was necessary to mention the idea. This task would be easier if we could just get rid of the legacy canvas. But that probably can't happen immediately, as we all know.
2016-05-03 17:13 GMT+02:00 Chris Pavlina <[email protected]>: > Oh god no. Can you imagine the bug reports from people who can't find > settings? > > http://i3.kym-cdn.com/photos/images/newsfeed/000/727/910/577.gif > > On Tue, May 03, 2016 at 04:41:20PM +0200, Nick Østergaard wrote: >> Maybe just show or enable the settings if the appropriate canvas is active? >> >> 2016-05-03 14:52 GMT+02:00 Wayne Stambaugh <[email protected]>: >> > 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 _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
