Re: [Kicad-developers] future developments: shared libraries and dynamic plugins

>Why doing triple work? It's not? >- C++ isn't exactly the best language for a reporting feature; Primarily when I say C++ right now, its the already existing options and not adding new ones. Could they be converted later? Maybe but the pcbnew/kicad format still need. > If you really want link in

Re: [Kicad-developers] future developments: shared libraries and dynamic plugins

On Wed, Nov 04, 2015 at 12:15:36PM -0500, Mark Roszko wrote: > It certainly wouldn't be closed off. It would simply be setup with > "generator" engines. > -xslt > -python > -C++ library > Each would implement a "generator engine" abstract class so they can be > swapped. Why doing triple work? -

Re: [Kicad-developers] future developments: shared libraries and dynamic plugins

It certainly wouldn't be closed off. It would simply be setup with "generator" engines. -xslt -python -C++ library Each would implement a "generator engine" abstract class so they can be swapped. Then each engine would decide how to execute the specified script or C++ library.The engines only ta

Re: [Kicad-developers] future developments: shared libraries and dynamic plugins

Le 04/11/2015 17:43, jp charras a écrit : > Le 04/11/2015 17:15, Mark Roszko a écrit : >> I eagerly await a plugin framework. I want play around with overhauling the >> netlisting/bom into plugins rather than XSLT and the C++ combo right now. >> I originally wanted to create a way more advanced XSL

Re: [Kicad-developers] future developments: shared libraries and dynamic plugins

: Wed, 4 Nov 2015 11:15:32 -0500 Předmět: Re: [Kicad-developers] future developments: shared libraries and dynamic plugins > I eagerly await a plugin framework. I want play around with overhauling the > netlisting/bom into plugins rather than XSLT and the C++ combo right now. > I originally

Re: [Kicad-developers] future developments: shared libraries and dynamic plugins

Le 04/11/2015 17:15, Mark Roszko a écrit : > I eagerly await a plugin framework. I want play around with overhauling the > netlisting/bom into plugins rather than XSLT and the C++ combo right now. > I originally wanted to create a way more advanced XSLT system complete > with configurable > display

Re: [Kicad-developers] future developments: shared libraries and dynamic plugins

I eagerly await a plugin framework. I want play around with overhauling the netlisting/bom into plugins rather than XSLT and the C++ combo right now. I originally wanted to create a way more advanced XSLT system complete with configurable displayed user options parsed from a definition XML but writ

Re: [Kicad-developers] future developments: shared libraries and dynamic plugins

On Sun, Nov 1, 2015 at 11:52 PM, Wayne Stambaugh wrote: > On 10/31/2015 6:04 PM, Cirilo Bernardo wrote: > > > > > > On Sun, Nov 1, 2015 at 6:35 AM, Wayne Stambaugh > > wrote: > > > > On 10/29/2015 4:16 AM, Cirilo Bernardo wrote: > > > Work so far on my part o

Re: [Kicad-developers] future developments: shared libraries and dynamic plugins

On 10/31/2015 6:04 PM, Cirilo Bernardo wrote: > > > On Sun, Nov 1, 2015 at 6:35 AM, Wayne Stambaugh > wrote: > > On 10/29/2015 4:16 AM, Cirilo Bernardo wrote: > > Work so far on my part of the 3D refactor has resulted in the > > development of a > >

Re: [Kicad-developers] future developments: shared libraries and dynamic plugins

On Sun, Nov 1, 2015 at 6:35 AM, Wayne Stambaugh wrote: > On 10/29/2015 4:16 AM, Cirilo Bernardo wrote: > > Work so far on my part of the 3D refactor has resulted in the > > development of a > > dynamic plugin scheme which has been shown to work on Linux, OSX, and > > MSWin. Although no plugins ar

Re: [Kicad-developers] future developments: shared libraries and dynamic plugins

On 10/29/2015 4:16 AM, Cirilo Bernardo wrote: > Work so far on my part of the 3D refactor has resulted in the > development of a > dynamic plugin scheme which has been shown to work on Linux, OSX, and > MSWin. Although no plugins are currently implemented which provide an actual > useful function I

Re: [Kicad-developers] future developments: shared libraries and dynamic plugins

fano Rossi Cc: KiCad Developers Subject: Re: [Kicad-developers] future developments: shared libraries and dynamic plugins Hi Cirilo and Stefano, Altium 3D viewer is more interactive than kicad 3d-viewer... It has the ability to move the 3D models directly in the viewer and can check a enclosure clearance or

Re: [Kicad-developers] future developments: shared libraries and dynamic plugins

On Thu, Oct 29, 2015 at 10:56 PM, Stefano Rossi wrote: > Cirilo, > > That sounds great. IMHO this goes along hand in hand with CERN's wishes of > making the different parts of kicad loadable libraries such as eeschema and > pcbnew. > > I don't really have much programming experience to recommend

Re: [Kicad-developers] future developments: shared libraries and dynamic plugins

Cirilo, That sounds great. IMHO this goes along hand in hand with CERN's wishes of making the different parts of kicad loadable libraries such as eeschema and pcbnew. I don't really have much programming experience to recommend an approach, but studying what already exists could help. Altium has

[Kicad-developers] future developments: shared libraries and dynamic plugins

Work so far on my part of the 3D refactor has resulted in the development of a dynamic plugin scheme which has been shown to work on Linux, OSX, and MSWin. Although no plugins are currently implemented which provide an actual useful function I think the improvements provided by the 3D model filenam