kicad-developers team mailing list archive

[Lorenzo Marcantonio <l.marcantonio@xxxxxxxxxxxx>]

On Wed, Aug 08, 2012 at 07:43:48AM +0200, Miguel Angel Ajo Pelayo wrote:

> * Provide a C++ interface (via classes or functions) [probably what we
> already have, the simpler the better]

OK, more or less is there

> * Then create a .i that %include / #include the .h to that file from
> the pcbnew/scripting directory,  [1]

That's the SWIG stuff, right? 

> * Then include your new .i at the end of
> http://bazaar.launchpad.net/~kicad-testing-committers/kicad/testing/view/head:/pcbnew/scripting/pcbnew.i

Uhmmmm... wasn't scripting in another branch? this seems to me the usual development branch I'm taking merge from... isn't the scripting branch this lp:~miguelangel-r/kicad/scripting ?

I got wxPython installed anyway, nothing difficult. The webpage instructions were totally misleading in fact! They include the full wx in wxPython because a) it seems it's really sensitive to version differences and b) it needs some addons anyway (like scintilla and other contrib stuff); pyshell works so I suppose that it's installed correctly.

*If* the scripting branch is up to date with the testing-committers one I should more or less be able to merge it in mine (I shouldn't have *fatal* conflicts, I'm not diverging too much, I hope...)

As for the keep-both-the-control-file-and-the-scripting-support I don't see it necessary: since there is anyway a (simple) syntax involved a user could be usefully copy a sample python script exactly like it would copy a sample sexp control file. I think, since the only thing I know of python is that you can't match code blocks with % in vi :P:P (that's an unforgivable thing coming from a C/LISP background...)

-- 
Lorenzo Marcantonio
Logos Srl