On Sep 21, 2013 11:53 AM, "ASM" wrote:
>
> Hi folks!
>
> I need your opinion about:
> * interprocess communication cvpcb<->eeschema<->pcbnew.
> * optimizational scripts (optimization work cycle)
> * the ability to change the scheme in pcbnew
>
> My usual scheme is a microcontroller and peripherals
On 09/21/2013 09:23 PM, Dick Hollenbeck wrote:
> I will fix it if it does not work on linux
Did that, it works now, and brilliantly.
We had a namespace collision on FPL_CACHE, my destructor was going into
LEGACY_PLUGIN's
FPL_CACHE destructor. Linker did not catch that, because geez, it wa
On Sat, Sep 21, 2013 at 11:32:56PM +0200, Miguel Angel wrote:
> > I would be interested in his spare time solve these issues. I think
> > for scripting would be ideal to take lua, since it can be built right
> > into the kicad (have MIT licence and less binary 100k code).
> > As the IPC to take POS
It doesn't look bad. I only used the standard "unitest" framework from
python.
It doesn't only look like a good way to keep the API binding/contract
checked,
but to do pcbnew unit testing from python-land.
http://bazaar.launchpad.net/~kicad-testing-committers/kicad/testing/revision/4336
+
http
Hi Leonid!,
2013/9/21 ASM
> Hi folks!
>
> I need your opinion about:
> * interprocess communication cvpcb<->eeschema<->pcbnew.
> * optimizational scripts (optimization work cycle)
> * the ability to change the scheme in pcbnew
>
> My usual scheme is a microcontroller and peripherals. Microconto
Great Martjin!!, just what I needed, for some reason I was looking for
"IGNORE_SYMBOLS" "IGNORE_METHODS" but couldn't find this
prfect! :)
* There are many swig artifacts that get documented: _object,
> SwigPyIterator. We must find a way to get rid of the
> classes that get accidentall
2013/9/21 Luke Kenneth Casson Leighton
> On Sun, Sep 8, 2013 at 12:23 AM, Miguel Angel wrote:
> >
> > It's a first try, only "BOARD" class extended descriptions are
> > imported from the C++ doxygen.
> >
> > It's not perfect, but can be automated and much better than nothing.
>
> ah, brilliant.
I'm looking for some known good P-CAD footprint libraries so I can
finish up testing the footprint library table implementation. If anyone
has any, please send them to me.
Thanks,
Wayne
___
Mailing list: https://launchpad.net/~kicad-developers
Post to
On Sun, Sep 8, 2013 at 12:23 AM, Miguel Angel wrote:
>
> It's a first try, only "BOARD" class extended descriptions are
> imported from the C++ doxygen.
>
> It's not perfect, but can be automated and much better than nothing.
ah, brilliant. actually the doxygen or epydoc conversion isn't so
cri
http://www.isitdownrightnow.com/launchpad.net.html
is the list working?
Miguel Angel Ajo Pelayo
http://www.nbee.es
+34 636 52 25 69
skype: ajoajoajo
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad
On 09/21/2013 03:39 AM, Miguel Angel wrote:
> Thoughts on this:
>
> * The pythonland libraries need a serious refactor, at this moment all
> functions and
> classes are brought together by swig into pcbnew.py: helper functions
> (LoadBoard,
> SaveBoard...)
> unit conversion macros, scripti
Hi folks!
I need your opinion about:
* interprocess communication cvpcb<->eeschema<->pcbnew.
* optimizational scripts (optimization work cycle)
* the ability to change the scheme in pcbnew
My usual scheme is a microcontroller and peripherals. Microcontoller
have many equivalent IO pins. I can use
On Sep 21, 2013, at 9:39 AM, Miguel Angel wrote:
> Thoughts on this:
>
> * The pythonland libraries need a serious refactor, at this moment all
> functions and
> classes are brought together by swig into pcbnew.py: helper functions
> (LoadBoard, SaveBoard...)
> unit conversion macros, s
Thoughts on this:
* The pythonland libraries need a serious refactor, at this moment all
functions and
classes are brought together by swig into pcbnew.py: helper functions
(LoadBoard, SaveBoard...)
unit conversion macros, scripting plugin definitions...
From the documentation perspective
14 matches
Mail list logo
