I am changing from a commercial package to Kicad (therefore directly started with v5.99 to avoid another migration path when v6 is released)
One of the things I have to figure out, is library organisation. Some commercial packages, I worked with, have the concept of ‘components’ (or ‘parts’)
A component has some properties, such as part number, value, tolerance. You can assign it a symbol from a symbol library, and a footprint from a footprint library.
So a single symbol definition, can be referred from different components with different values, order codes and footprints.
When looking at Kicad, it seems to me, this is more or less equivalent to symbol inheritance.
Is this assumption correct ? e.g. I can have a single capacitor symbol, which is forms the base for all capacitors. Where each capacitor shows this symbol, but has its own properties.
(and if I update the ‘base’ symbol all capacitors derived from it will reflect the changes ?)
If it works like this, are there any limitations compared the ‘component’/‘parts’ approach, some others use ?