kicad-developers team mailing list archive

[Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>]

I think *all* the functions are exposed right now, but if they return
complex types, you may need to link them up with python concepts in
the .i files.

If you read through the C++ code, looking at how tracks and vias are
added, you can try those same names and concepts through swig,
starting with an example like createPcb.py or printo.py, which is in
the archives of this list.

I'm making slow progress here, but I *think* my scripting PPA works
again, and follows "the right rules" for Ubuntu/Debian--however,
there's a regression in scripting since r4018, where the nice
encapsulation in the C++ world hasn't made it into the SWIG side yet.
Matthew created a patch for it, which works, but Miguel brought up a
good point about just nixing the python encapsulation for those
functions.

If it hasn't been fixed by tonight, I plan on submitting a patch
request tonight that removes the encapsulation as Miguel brought up
and then the example scripts will work again.

Adam Wolf
Wayne and Layne, LLC

On Tue, Apr 9, 2013 at 9:41 AM, Dick Hollenbeck <dick@xxxxxxxxxxx> wrote:
> On 04/09/2013 09:32 AM, Senthil Seveelavanan wrote:
>> Great,
>>
>> I am fully prepared to help out.
>>
>> However, I only have a little C++ experience, and no swig experience...
>> How do I determine which functions are exposed?
>>
>> How should drawing tracks work? set_track(....) etc
>>
>> > The entire KiCad project is the result of volunteer effort"
>> I am aware - but thanks again everybody
>>
>> Senthil
>
>
> You can also get a $ quote from Miguel to help you for a fee.
>
> Time is money.  If it saves you time, it could save you money.
>
>
>
>
>
> _______________________________________________
> 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