> I will keep working on it, and keep you updated, my "roadmap" may look like
> this:
>
> 1) End the wrapper for BOARD objects, and all the objects inside a board.
> 1.b) Add wrappers to basic objects like wxString, wxPoint, etc...
> 1.c) Clean up the GetBoard() implementation I did now (just fo
Dick, Thanks a lot for the feedback.
1) I suspected that the wxString was used to take care of filename
encondigs. It makes sense. Thanks for your confirmation.
I'll try to look at the wxPython project to see how do they handle the
wxString objects :)
2) Sorry for my poor explanations, I will try
On 03/05/2012 07:23 AM, Miguel Angel Ajo Pelayo wrote:
> Well, I managed to wrap the DLIST templates after fixing some strange
> inheritance
> behaviour in swig (via %ignore directives).
>
> And everything seems to start working with the lists from BOARD object.
Congratulations! Thanks for your
As a proof of concept (with randomly swig-ed classes, etc...):
http://bazaar.launchpad.net/~miguelangel-r/kicad/scripting/revision/3444
With little work I managed to link to python and include a couple of
SWIG-ed modules
from our own code/classes.
The integration in pcbnew.cpp and CMakeList.txt
Hi Dick,
2012/2/27 Dick Hollenbeck
> On 02/27/2012 01:48 AM, Miguel Angel Ajo Pelayo wrote:
> > I've been doing some experiments about that during the weekend, with
> python as a first
> > target, and using SWIG (which should be highly desired, as it's
> something easier to
> > mantain).
> >
> >
On 02/27/2012 01:48 AM, Miguel Angel Ajo Pelayo wrote:
> I've been doing some experiments about that during the weekend, with python
> as a first
> target, and using SWIG (which should be highly desired, as it's something
> easier to
> mantain).
>
> And by now, what I found is that swig is quite
Awesome, this is good news. In case you wanna dig more into this, I'll
be happy to test any patch or early code development.
It's also worth noting that SWIG isn't the only way to access C/C++
libraries from within Python.. these are some of the other ways:
Cython http://cython.org/
Pyrex http
I've been doing some experiments about that during the weekend, with python
as a first target, and using SWIG (which should be highly desired, as it's
something easier to mantain).
And by now, what I found is that swig is quite mature, but mainly ready for
this:
Python--->[extension]/extensio
Sorry, I ignore the "_wrapper.cxx + yyy_wrapper.cxx + etc cannot be
linked together"... swig define them as static functions, so they can be
linked together and will work. The path is not that dark ;-)
2012/2/27 Miguel Angel Ajo Pelayo
> I've been doing some experiments about that during t
+1 on choosing Python over LUA or JS. Blender is using Python as
scripting language and also internally.. and I guess Blender's
requirements are pretty similar to those of KiCad.
On 02/24/2012 09:22 PM, Miguel Angel Ajo Pelayo wrote:
About python, yes, I think it fits the same way lua does, a
About python, yes, I think it fits the same way lua does, and I'm my
opinion, it has more libraries
that can be useful for the scripts (like image manipulation, etc...). There
wasn't a branch already
trying this, how good or bad did it go?
and about "a", honestly, I'd really like to say yes, but I
On 02/24/2012 12:42 PM, Miguel Angel Ajo Pelayo wrote:
> Hehe, that can be another option, yeah!,
>
>I've worked with lua before, tuned the garbage collector to work in deeply
> embedded
> devices (under 32kB of RAM) and
> wrapped some libs by
> hand:
> http://code.google.com/p/espardino/so
Hehe, that can be another option, yeah!,
I've worked with lua before, tuned the garbage collector to work in
deeply embedded devices (under 32kB of RAM) and
wrapped some libs by hand:
http://code.google.com/p/espardino/source/browse/#svn%2Ftrunk%2Fopenlibs%2Flua
I think Javascript is incred
On 02/24/2012 08:54 AM, Miguel Angel Ajo Pelayo wrote:
Ok, I changed the topic of this thread, to match the discussion, which
is about making Kicad fully scriptable in Javascript.
For speed reasons, and wide adoption, it seems that V8 must be
our preferred engine.
Hi Miguel,
Did you consider
2012/2/24 Dick Hollenbeck
> Thanks Miguel. Can you clearly state the the SWIG support for V8, which
> is still external
> to the SWIG project, is ready for production use? Or do you still have
> doubts?
>
As I said in some previous email, it needs heavy testing, that I will do
:-)
> That was
Thanks Miguel. Can you clearly state the the SWIG support for V8, which is
still external
to the SWIG project, is ready for production use? Or do you still have doubts?
That was the original question.
I also appreciate the use cases being identified up front. I noticed you also
did not say
16 matches
Mail list logo
