kicad-developers team mailing list archive

[jp charras <jp.charras@xxxxxxxxxx>]

Le 05/11/2014 23:53, Nick Østergaard a écrit :
> 2014-11-05 23:40 GMT+01:00 LordBlick <lordblick@xxxxxxxxx>:
>> In response to a message written on 03.11.2014 15:14, from Jean-Samuel
>> Reynaud:
>>>
>>> Hi All,
>>>
>>> I wrote few months ago an extension to be able to write in python a
>>> footprint library plugin.
>>> ie: for the moment for footprint you have to choice between:
>>> - Kicad
>>> - Legacy
>>> - GitHub
>>> ...
>>> And I had write a "Python". You choose the python module to load (the
>>> module name as an option of the python plugin) and this python
>>> module have to implement some functions to do the job.
>>>
>>> This code is currently under a branch :
>>> lp:~kicad-developers/kicad/python_plugin
>>>
>>> Specific code is mainly in pcbnew/fppython/ and there is a python
>>> example in pcbnew/fppython/fppython_example.py.
>>
>> IMHO that plugin should be named „pyDynamicFootprint” or similar.
>> Instead of creating a long library from 4 to 64 pins we can easily generate
>> desired package footprint on demand.
> 
> How do you select it? There is also the footprint wizzards.

Wayne and I are thinking the main (the only one) purpose of this python
plugin is to allow import of footprint libraries coming from an other
EDA tool,
not to create a new footprint wizard (There is already a more powerful
python wizard mechanism in Kicad).

The advantage of a python plugin to import foreign libraries is the fact
the python code is outside the main kicad code, and can be
written/maintained by guys who are not specialist of internal Kicad code.

fppython_example.py looks like a wizard, but this is just a short python
example, not a good example of the interest of a python plugin

-- 
Jean-Pierre CHARRAS