kicad-developers team mailing list archive
Mailing list archive
Re: thoughts on hierarchical schematics
Kicad implemented hierarchy in a way that was different than how it was
usually done by the rest of the industry. The fix is to see how everyone
does it and do it the same way.
1) Projects and Libraries merge into a single entity . The project that you
design and upload to github.com is download by your users as a library. So
your project and library file formats must dovetail so that one design repo
satisfies both at the same time. The libraries that you downloaded were
once someone else's project
2) Add bottoms up design. Kicad needs a "Make Symbol" menu pick to create a
symbol from the schematic.
3) Store the current hierarchical symbols created by top down kicad design
in the same file format as bottoms up symbols.
Do those three things and start using attributes and your problems will be
On Fri, Dec 27, 2019 at 8:38 AM Tjeerd Pinkert <
> Dear list,
> some has probably already been discussed here. I'm diving a bit further
> into hierarchical schematics at present. I'm trying to creating "module"
> schematics that are version controlled in Git, only schematics at this
> moment, and I'm missing some things that would be nice to have in that
> area. Currently also some behaviour of Kicad is a bit counter intuitive
> at that point with regard to where stuff is stored in the files.
> The attached file contains some thoughts on this from a user
> perspective. Basically some use cases that, I hope, become possible in
> the future... (no, not expecting this in 6 or even 7, but some day...)
> Any comments are welcome, also on how to formulate this such that it
> could become points on the roadmap?
> Best regards,
> Tjeerd Pinkert
> 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