kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #27644
Re: for comment: legacy canvas in V5 release
-
To:
Chris Pavlina <pavlina.chris@xxxxxxxxx>, Cirilo Bernardo <cirilo.bernardo@xxxxxxxxx>
-
From:
Tomasz Wlostowski <tomasz.wlostowski@xxxxxxx>
-
Date:
Wed, 8 Feb 2017 00:08:32 +0100
-
Authentication-results:
spf=pass (sender IP is 188.184.36.46) smtp.mailfrom=cern.ch; lists.launchpad.net; dkim=none (message not signed) header.d=none;lists.launchpad.net; dmarc=bestguesspass action=none header.from=cern.ch;
-
Cc:
KiCad Developers <kicad-developers@xxxxxxxxxxxxxxxxxxx>
-
In-reply-to:
<20170207225723.GB24887@beast.local>
-
Spamdiagnosticmetadata:
NSPM
-
Spamdiagnosticoutput:
1:99
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
On 07.02.2017 23:57, Chris Pavlina wrote:
> I suggested something related earlier. Here is what I would do:
>
> - Merge OpenGL and Cairo!!! The average user doesn't know what a Cairo
> is, or what a GAL is. We're lucky if they know what an OpenGL is.
> OpenGL and Cairo should just be "Pcbnew", with a fallback from GL to
> Cairo if GL can't start and a "Disable hardware acceleration" option
> in the preferences to do it manually.
>
> - Rename legacy/default to "Legacy Pcbnew", also make this an option in
> the preferences.
Agreed!
In the meanwhile, I have to do the infamous drag component with traces
connected for the GAL... :/
Cheers,
Tom
>
> Both of these new options should default false.
>
> On Wed, Feb 08, 2017 at 09:52:59AM +1100, Cirilo Bernardo wrote:
>> Given the recent thread on making Legacy a build option and
>> after a number of conversations with people familiar with the
>> source code, it seems that a number of developers believe
>> that the Legacy canvas code is really holding back a lot of
>> improvements to the code structure. I would suggest that in
>> the V5 release, each time pcbnew is started it should always
>> default to GAL (or Cairo if someone is using a laptop from 2001).
>> On top of that, each time a user decides to switch to the Legacy
>> canvas I would throw up a nag screen to tell the user that the
>> canvas they are selecting has been deprecated and will be
>> removed in the next release and that the user should use the
>> GAL canvas instead and report any missing or buggy tools
>> via the bugtracker.
>>
>> I think ripping out Legacy soon after release would be a good
>> thing and will allow (some of us) to concentrate on improved
>> modularity (and maintainability) of the code. Encouraging
>> people to use GAL in V5 (while also discouraging them from
>> using Legacy) should hopefully get us the bug reports we need
>> to implement and polish up the GAL tools.
>>
>> Any comments?
>>
>> - Cirilo
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help : https://help.launchpad.net/ListHelp
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
References