kicad-developers team mailing list archive

[Jeff Young <jeff@xxxxxxxxx>]

Thinking more about it, we could probably auto-convert existing aliases to inheritance when we read them in.  It would certainly be easier to support only one UI (and the alias UI is problematic anyway).

Wayne sent out a proposal on the dev list a while back.  I know I read them so they must have been sent out as PDF or Word or something, but the only links I could find are for OpenDocument: https://lists.launchpad.net/kicad-developers/msg35233.html

> On 16 Jul 2018, at 14:28, Simon Richter <Simon.Richter@xxxxxxxxxx> wrote:
> 
> Hi,
> 
> On 16.07.2018 11:19, Jeff Young wrote:
> 
>> Do we plan on having inheritance replace aliases?
> 
> I do, but you might have noticed that with all my other commitments that
> isn't worth much.
> 
> Do we have a spec document beyond what was discussed on IRC?
> 
>> If so, what do we do with old symbols?  (Will we have to support both paradigms?)
> 
> It should be possible to keep them usable, except that they won't be
> part of the hierarchy. If we have special rules for replacement inside
> the hierarchy, e.g. two transistor symbols that have inherited the same
> SPICE type and graphics are obviously exchangeable, while symbols
> outside the hierarchy are more difficult.
> 
>   Simon
> 
> _______________________________________________
> 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