pointhi
commented
5 years ago The scripts directory is currently considered wild-west when thinking about coding guidelines. You can find a variety of different approaches and those are mainly there to help people generate additional footprints when required, but are not considered as easy to use with defined rules.
It is preferable to follow some existing scheme unless you think you have an interesting approach which would improve the whole task. In long term, we would like to move to kicad-python where a strict coding and data-structure policy would be in place. But to create those, some experiments how such a policy should look like need to be carried out, as you see in the current wild-west style :)
https://github.com/pointhi/kicad-footprint-generator/issues/55 https://forum.kicad.info/t/rfc-future-of-footprint-wizard-and-generator/12592
I'd like to contribute to the KiCad libraries and really like the idea of the generators. Even though I'm a longtime programmer, it's hard for me to dive in. I've read the KLC and inspected older and newer generator scripts (based on CSV and YAML). However, I did not find general coding rules and specifications for the generators or objects (symbols/footprints) to create - beside the KLC.
Are there some additional guidelines or are there just the sources? Am I free with the YAML files, as long as I use already used "keywords" or is there a YAML dictionary or specification?