Re: [Kicad-developers] [RFC] Documentation for pcbnew plugins

Simon, I committed your patch to the master branch. I cleaned up the formatting, removed trailing whitespace, and added a table of contents. If I broke any formatting, please let me know. In the future, please limit you column width to 80 or 100 for markdown files. It's also a good idea to add

Re: [Kicad-developers] [RFC] Documentation for pcbnew plugins

Find the patch attached in case there are no objections from someone else. Best Regards Simon Am 2017-06-27 21:49, schrieb Wayne Stambaugh: This looks good. Anyone else find any issues with it? You do not need to change the Doxygen configuration files. Someone modified them to use all

Re: [Kicad-developers] [RFC] Documentation for pcbnew plugins

This looks good. Anyone else find any issues with it? You do not need to change the Doxygen configuration files. Someone modified them to use all *.md files in the appropriate search paths. Please post the patch created by git format-patch and post it as an attachment and I will commit it if

Re: [Kicad-developers] [RFC] Documentation for pcbnew plugins

I made some adjustments to the documentations. https://github.com/skuep/kicad-source-mirror/blob/devel/Documentation/development/pcbnew-plugins.md I did not write something about adding paths to the python runtime environment since I don't use this feature (and don't want to ;-)) because I don't

Re: [Kicad-developers] [RFC] Documentation for pcbnew plugins

I am sorry, I did not mean to rush things. I will look over your suggestions :-) Thanks! Am 17.06.2017 um 15:41 schrieb Wayne Stambaugh: > Simon, > > Please be patient. I know things have been a bit slow on the mailing > list recently. This is not that unusual in the summer as developers are >

Re: [Kicad-developers] [RFC] Documentation for pcbnew plugins

Simon, Please be patient. I know things have been a bit slow on the mailing list recently. This is not that unusual in the summer as developers are on vacation or busy doing other things. I took a look at your document and have the following comments: Avoid referring to the Python plugin as a

Re: [Kicad-developers] [RFC] Documentation for pcbnew plugins

Since there hasn't been any followup, attached is the patch. Best Regards!From 76b31cda55b725ca60e4f8bf10167f97d0da0416 Mon Sep 17 00:00:00 2001 From: Simon Kueppers Date: Thu, 15 Jun 2017 11:27:33 +0200 Subject: [PATCH] Started documentation for pcbnew plugins ---

Re: [Kicad-developers] [RFC] Documentation for pcbnew plugins

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

[Kicad-developers] [RFC] Documentation for pcbnew plugins

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