← Back to team overview

kicad-developers team mailing list archive

Re: Packaging the python footprint wizards for the release

 

I just committed a fix so at least the python plugins will get installed
in share/kicad/scripting which seems to work properly on msys2/mingw64
builds.  I'll test it on Linux when I get a chance.  I'm going to pass
on the python scripting example folder unless someone can confirm that
all of the example python scripts work correctly.

On 9/30/2015 11:59 AM, Nick Østergaard wrote:
> So what exactly are we going to do?
> 
> We need to fix up the CMake files and the real search paths.  What
> should the paths be?
> 
> 
> 2015-09-30 15:51 GMT+02:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
>> The contents of the pcbnew/scritping/plugins folder will be installed
>> which contains the scripts you are describing.  It currently is not
>> installed on windows or linux.  Ironically it is install on osx.  I'm
>> not sure how that happened.  The contents of pcbnew/scripting/examples
>> will not be installed unless someone verifies that they run without
>> issue.  As Miguel suggested, the example scripts may be broken due to
>> changes in the board API.  I would rather not install broken examples
>> since the plugin scripts can also serve as examples.
>>
>> On 9/30/2015 9:35 AM, easyw wrote:
>>> Hi Wayne,
>>> please reconsider to leave the python wizard installed
>>> The wizard is giving:
>>> BGA, DIP/SIP, QFP, Circular array and BarCode just out of the box.
>>>
>>> May be they are improvable (exposed pad, thermal vias etc), but at this
>>> state they are fully usable (without any crash or prob) and much faster
>>> then standard footprint editor.
>>> Moreover, if you do not include them you get a wizard button in pcbnew
>>> footprint editor for nothing...
>>>
>>>
>>>
>>> On 30/09/2015 14.30, Wayne Stambaugh wrote:
>>>> Thanks for the update.  I'll leave the python examples uninstalled until
>>>> we can confirm that they are not broken.  I don't think it's all that
>>>> important for the stable release.  Users can always look at the python
>>>> plugins to get an idea of how the python scripting works.
>>>>
>>>> On 9/30/2015 3:59 AM, Miguel Angel Ajo wrote:
>>>>> I agree with JP here, QFP and QFN may be separate wizards. If there are
>>>>> common parts, feel free to use inheritance from a common base to reuse
>>>>> code.
>>>>>
>>>>> About naming: footprint generators sound better, or whatever, at that
>>>>> time I was following an industry leader on naming it..., but I agree
>>>>> footprint generator is more clear for the task.
>>>>>
>>>>> About including our scripting examples, I wouldn't, those are not tested
>>>>> with the current codebase, and likely to be broken because of C++
>>>>> interface changes.
>>>>>
>>>>> Sorry for my slow response,
>>>>> best regards,
>>>>> Miguel Ángel.
>>>>>
>>>>>
>>>>> jp charras wrote:
>>>>>> Le 30/09/2015 01:25, Wayne Stambaugh a écrit :
>>>>>>> JP,
>>>>>>>
>>>>>>> Your name is on the initial commit for qfn_wizard.py.  I don't have
>>>>>>> time
>>>>>>> to figure out these patches should be included.  Do these patches make
>>>>>>> sense?  Let me know so I can make a decision on whether or not to
>>>>>>> commit
>>>>>>> them.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Wayne
>>>>>>>
>>>>>>
>>>>>> These patches make sense, I used them to fix bugs in our footprint
>>>>>> wizard dialog issues, and issues in some pythons scripts (mainly usage
>>>>>> of print command which created python exceptions when stdout was never
>>>>>> read, especially on Windows).
>>>>>>
>>>>>> But do not commit them. Reasons:
>>>>>> - I am thinking the wizard to create a QFN should be an other wizard
>>>>>> than the QFN wizard.
>>>>>> The thermal pad needs many parameters, useless for a QFN without
>>>>>> thermal
>>>>>> pad.
>>>>>> - The wizard to create a QFN with thermal pad needs refinements, before
>>>>>> being committed
>>>>>>
>>>>>> I'll have a look at that later.
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list: https://launchpad.net/~kicad-developers
>>>>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>>>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~kicad-developers
>>>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp


Follow ups

References