The problem I would like to mitigate largly arrised because of big repositories like for example: https://github.com/KiCad/Connectors_Phoenix.pretty
Those repositories contain multiple hundreds of footprints, and I think it would be a bad idea to further split them. Instead of, I would likely see the feature to group them together by series for example. This thread is supposed to create a discussion about the general idea, as well as how different solution would work out. Which means it would be especially improtant to be discussed by Library Maintainers (@SchrodingersGat, @Rene_Poschl, @jkriege2,…) as well as developers (@nickoe, …)
My proposal would allow us to nest footprints inside groups visualized by the kicad viewer. Those are generated based on informations inside the .pretty repo.
Currently, I have two ideas how we could achive that:
Add a additional group keyword in the footprint module, which is then used by the viewer
- should be fully backward compatible
- repos still contains multiple hundreds of footprints in one directory
- structure is not represented in the normal file explorer
Support of Directories in the .pretty format
- structure inside kicad and external ones matches
- easier to refactor
- not backward compatible
What are your thoughts about this idea?