Hi,
On 07/16/2018 04:24 PM, Tomasz Wlostowski wrote:
> Why do we need any inheritance at all? My only guess is to make Kicad
> even more hackerish and difficult to understand.
It would allow getting rid of the really annoying redundancies in the
library:
- all transistor symbols exist in six
Even though I'm not quite ready to start discussing the new file formats
just yet, here a few of my thoughts on inheritance:
Inheritance will be implemented in a second phase during the development
of the new file formats and possibly pushed into the version 7 release.
The reason is that there is
My guess would be maintainability.
Having some way of sharing parts of different symbols with each other
makes it way easier to manage large libs. (Nobody would be forced to use
these features but they can make live easier for library maintainers. We
could then for example provide a single
On 16/07/18 16:04, Jeff Young wrote:
> Thinking more about it, we could probably auto-convert existing aliases to
> inheritance when we read them in.
Why do we need any inheritance at all? My only guess is to make Kicad
even more hackerish and difficult to understand.
Tom
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
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?
Do we plan on having inheritance replace aliases?
If so, what do we do with old symbols? (Will we have to support both
paradigms?)
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe
7 matches
Mail list logo
