Small followup. 1. It might be worthwile to also include informations on how to expose something you might have implemented in the KiCad C/C++ code via SWIG to python. But I don't know about this stuff, this might have to do someone else.
2. I think this document should also incorporate some conventions that we want to see with plugins in the future. for example, should action scripts start with "action_" in the filename? (This is already the case with the action scripts shipped with KiCad). Best Regards Am 15.06.2017 um 11:32 schrieb Simon Küppers: > Hi everyone, > I started writing down what I learned recently while started developing > on a pcbnew plugin. > > As Wayne suggested, I created a new markdown file in the developers > documentation. You can view it in my github repo > https://github.com/KiCad/kicad-source-mirror/compare/master...skuep:devel?short_path=8efcfb4#diff-8efcfb4e0c1a503ca34f0304450b9dc6 > > Could you all check if the information is sound? I will generate a diff > when I feel the documentation is somewhat ready. > > Best Regards > Simon > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
