On 03/05/2012 07:23 AM, Miguel Angel Ajo Pelayo wrote:
Well, I managed to wrap the DLISTxxx 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
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 for test)
Hi Dick,
2012/2/27 Dick Hollenbeck d...@softplc.com
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).
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
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 miguelan...@nbee.es
I've been doing some experiments
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:
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
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
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
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
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.
V8 comes just with the javascript JIT interpreter, and no more. It's ready
to link
11 matches
Mail list logo