kicad-developers team mailing list archive

[Bernhard Stegmaier <stegmaier@xxxxxxxxxxxxx>]

Hi,

I don’t know how it fits together (I never get the direction of scripting right… outside of KiCad or inside), but…
    if sys.platform.startswith('darwin'):
        for singlepath in sys.path:
            if os.path.isdir( os.path.join( singlepath, 'scripting', 'plugins') ):
                plugin_directories.append( os.path.join( singlepath, 'scripting', 'plugins') )
shouldn’t this be the same/similar as set in pcbnew?
    // User scripting folder (~/Library/Application Support/kicad/scripting/plugins)
    pypath = GetOSXKicadUserDataDir() + wxT( "/scripting/plugins" );

    // Machine scripting folder (/Library/Application Support/kicad/scripting/plugins)
    pypath += wxT( ":" ) + GetOSXKicadMachineDataDir() + wxT( "/scripting/plugins" );

    // Bundle scripting folder (<kicad.app>/Contents/SharedSupport/scripting/plugins)
    pypath += wxT( ":" ) + GetOSXKicadDataDir() + wxT( "/scripting/plugins" );
Instead of just using sys.path set somewhere else as base?


Regards,
Bernhard

> On 17 Mar 2015, at 07:12, Miguel Ángel Ajo <majopela@xxxxxxxxxx> wrote:
> 
> Nice Adam!
> 
> I wonder what happens with the console, basically it fires up, but most 
> keystrokes are handled as shortcuts..
> 
> In the other hand plugin (footprint wizard) loading doesn’t show
> any wizard (and we bundle a few).
> 
> (Open footprint editor -> New footprint using wizard)
> check if we’re providing correct env vars, and if this code is valid enough for our OS X bundling.
> http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/view/head:/scripting/kicadplugins.i#L70 <http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/view/head:/scripting/kicadplugins.i#L70>
> 
> Otherwise we could extend the places were python looks for plugins at start if that were necessary.
> 
> Best,
> Miguel Ángel.
> 
> Miguel Ángel Ajo
> 
> On Monday, 16 de March de 2015 at 19:34, Adam Wolf wrote:
> 
>> Hi folks,
>> 
>> There is a debug night build of Python scripting on OS X, thanks to Collin. I haven't switched it over because the scripting console is messed up.  I posted details on the list a few weeks ago, but here's the link.
>> 
>> http://downloads.kicad-pcb.org/osx/DEBUG/ <http://downloads.kicad-pcb.org/osx/DEBUG/>
>> 
>> If folks think I should switch it over to be the regular nightlies, I can do that no problem.
>> 
>> Adam Wolf
>> Cofounder and Engineer
>> W&L
>> 
>> 
>> On Mon, Mar 16, 2015 at 1:13 PM, Wayne Stambaugh <stambaughw@xxxxxxxxx <mailto:stambaughw@xxxxxxxxx>> wrote:
>>> I hope we can get Python scripting working on OSX before the stable
>>> release but I cannot guarantee it.  Building OSX binaries has been
>>> difficult to say the least but I think we're close.  The OSX devs can
>>> probably give you a better idea than I can.
>>> 
>>> On 3/14/2015 5:00 PM, Jean-Paul Louis wrote:
>>> > I still cannot build with Python Scripting enabled in OS X,
>>> > and the build made by Adam was not working (Python console unusable)
>>> >
>>> > Will that be fixed before stable release? I am not using it yet because of this.
>>> >
>>> > Just curious,
>>> > Jean-Paul
>>> > AC9GH
>>> >
>>> >
>>> >> On Mar 14, 2015, at 2:47 PM, Wayne Stambaugh <stambaughw@xxxxxxxxx <mailto:stambaughw@xxxxxxxxx>> wrote:
>>> >>
>>> >> As you all know we are currently working towards a stable release.  I
>>> >> need to get and idea of what open items are left before I declare a
>>> >> feature freeze.  Here is the list of things I know about:
>>> >>
>>> >> * Environment variable path edit dialog (me, in progress).
>>> >> * Add bitmaps and missing entries to GAL canvas context menu (CERN).
>>> >> * Python API (Miguel).
>>> >> * OSX track pad (Garth).
>>> >>
>>> >> Are there any other features that are on the radar for the next stable
>>> >> release?  I will make exceptions on a case by case basis after the
>>> >> freeze but I don't want to get blind sided by any unexpected feature
>>> >> requests the week before the stable release.
>>> >>
>>> >> We need to go through the bug tracker and make sure we don't have any
>>> >> known severe bugs which cause crashes and/or data loss that have not
>>> >> been tagged fix committed and take the appropriate action.  This number
>>> >> will have to be zero before I will make the stable release.  Obviously I
>>> >> would like to get as many of non-critical bugs fixed as well.
>>> >>
>>> >> What is the current status of the documentation and it's CMake build
>>> >> configuration code?  Are we far enough along that we can move the repo
>>> >> to https://github.com/KiCad <https://github.com/KiCad>?  I want all of the "official" KiCad repos
>>> >> there for obvious reasons.  We also need to get this set up soon so the
>>> >> documentation for the new router features can be added which I'm
>>> >> guessing will take awhile.  I will give all of the necessary document
>>> >> developers commit access to that repo once it is set up.  I'm going to
>>> >> let the doc developers handle the pull requests so I can keep my
>>> >> involvement to a minimum.  Also, what about nightly builds of the
>>> >> documentation?  We will need them as well.
>>> >>
>>> >> I think we are in pretty good shape as far as nightly builds go for all
>>> >> of the major platforms.  Thanks to all of you who have worked tirelessly
>>> >> on this.  If we are missing anything in this regard, please help out if
>>> >> you can so we can have as many bases covered as possible once the stable
>>> >> release is out.
>>> >>
>>> >> Hopefully I can announce the feature freeze in the next few weeks so we
>>> >> can start focusing on the stable release.
>>> >>
>>> >> Thank you all for efforts.  I hoping the next stable release of KiCad
>>> >> will meet the needs of our users.
>>> >>
>>> >> Cheers,
>>> >>
>>> >> Wayne
>>> >>
>>> >> _______________________________________________
>>> >> Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
>>> >> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>>> >> Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
>>> >> More help   : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
>>> >
>>> 
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
>>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>>> Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
>>> More help   : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
>> 
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
>> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>> Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
>> More help : https://help.launchpad.net/ListHelp <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