kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

This is not entirely accurate.  All new features must be implemented in
GAL at a minimum.  Implementing the same feature in the legacy canvas is
optional.  The only requirement is that any objects created in the GAL
canvas must be properly rendered in the legacy canvas even if they
cannot be edited.

On 4/30/2017 11:31 PM, José Ignacio wrote:
> It's been established that new features have to work with GAL, but they
> don't need to work with legacy. What's not allowed yet is to BREAK
> legacy by implementing a new GAL-only feature.
> 
> On Sun, Apr 30, 2017 at 9:43 PM, Simon Richter <Simon.Richter@xxxxxxxxxx
> <mailto:Simon.Richter@xxxxxxxxxx>> wrote:
> 
>     Hi,
> 
>     what is the current outlook on the legacy canvas past v5?
> 
>     Specifically, I have a feature branch that targets v6 because it
>     certainly won't be in time for v5. Does it make sense to invest effort
>     here to get it working with the legacy canvas?
> 
>        Simon
> 
> 
>     _______________________________________________
>     Mailing list: https://launchpad.net/~kicad-developers
>     <https://launchpad.net/~kicad-developers>
>     Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>     <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>     Unsubscribe : https://launchpad.net/~kicad-developers
>     <https://launchpad.net/~kicad-developers>
>     More help   : https://help.launchpad.net/ListHelp
>     <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
>