kicad-developers team mailing list archive

[Bernhard Stegmaier <stegmaier@xxxxxxxxxxxxx>]

And maybe a dumb question, but… how do I get some debugging output from kicadplugins.i?
Will a simple Python print() show something? Where?

Regards,
Bernhard

> On 28 Sep 2015, at 23:01, Bernhard Stegmaier <stegmaier@xxxxxxxxxxxxx> wrote:
> 
> OK.
> I’ll play around a bit with it on the weekend.
> If it is really only about adding the system (== application bundle) path to kicadplugins.i, it could be quite easy.
> 
> The path itself is just a matter of definition… but for the sake of consistency, it IMHO should use a pattern similar to the other OSs.
> 
> You then still can decide if you want it for the stable release.
> Might cause some problems, because I bet almost nobody on OS X did do anything serious with python…?
> 
> 
> Regards,
> Bernhard
> 
> 
>> On 28 Sep 2015, at 22:49, Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
>> 
>> I'm not sure about the appropriate path on osx.  Even on osx, the python
>> scripts only get installed when the python scripting build is enabled so
>> Adam must be building the python scripting on osx.
>> 
>> Looking at kicadplugins.i, it definitely will not find the system
>> install path for the plugin python scripts.  I'm not sure I want to mess
>> with it too much before the stable release.  The python scripting
>> support code could use some love.
>> 
>> On 9/28/2015 4:36 PM, Bernhard Stegmaier wrote:
>>> Where should I find it?
>>> I thought I read somewhen it should be somewhere under Tools->…?
>>> 
>>> I just checked Adams last build and I only see "Tools->Scripting Console”, nothing else.
>>> The python files seem to be contained in the application bundle, although at a place that doesn’t seem to match anything from the other platforms:
>>> <kicad.app>
>>>   … +- SharedSupport => that’s the base path for all additionally shipped things
>>>            +- plugins   =>  here are the xls files
>>>            +- scripting
>>>                +- plugins   => here are the python files
>>> 
>>> I think this is some old stuff I did pretty much without knowing anything about scripting or plugins…
>>> If there is an agreement on how it is done on the other platforms (xslt vs. python), I could make it the same for OS X.
>>> 
>>> Anyway… the kicadplugins.i is IMHO definitely wrong and doesn’t match anything of the other compiled-in paths.
>>> You may be lucky to get it working with some magic $KICAD_PATH and $PATH settings.
>>> 
>>> 
>>> Regards,
>>> Bernhard
>>> 
>>>> On 28 Sep 2015, at 22:02, Nick Østergaard <oe.nick@xxxxxxxxx> wrote:
>>>> 
>>>> The python based footprint wizards does not use the python console...
>>>> 
>>>> 2015-09-28 21:50 GMT+02:00 Bernhard Stegmaier <stegmaier@xxxxxxxxxxxxx>:
>>>>> Hi,
>>>>> 
>>>>> I guess the paths defined in this kicadplugins.i are also pretty useless for OS X:
>>>>> * This will never reach the <kicad.app Bundle>/Contents/SharedSupport/plugins/ folder where the shipped plugins will probably go into
>>>>> * It should add probably some $HOME/Library/Application Support/kicad/plugins folder for user defined script plugins
>>>>> (Except you have those paths in your system $PATH, what you normally won’t want to…)
>>>>> 
>>>>> Should this be changed for stable release for OS X?
>>>>> Will the stable release be shipped with scripting support on OS X?
>>>>> Last time I tried it wasn’t really usable because of the clashes with the menu hotkeys in the python console…
>>>>> 
>>>>> 
>>>>> Regards,
>>>>> Bernhard
>>>>> 
>>>>>> On 28.09.2015, at 20:56, LordBlick <lordblick@xxxxxxxxx> wrote:
>>>>>> 
>>>>>> In response to a message written on 28.09.2015, 20:31, from Wayne Stambaugh:
>>>>>>> Maybe we should put the python scripts in share/kicad/scripting/python
>>>>>> +1
>>>>>>>>>> ${KICAD_PATH}/scripting/plugins
>>>>>>>>>> ${HOME}/.kicad_plugins
>>>>>>>>>> ${HOME}/.kicad/scripting/plugins
>>>>>> Also with minimum, add ${HOME}/.local/share/kicad/scripting/python
>>>>>> here.
>>>>>> --
>>>>>> Best Regards,
>>>>>> LordBlick
>>>>>> 
>>>>>> _______________________________________________
>>>>>> 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
>>> 
>> 
>> _______________________________________________
>> 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