kicad-developers team mailing list archive

[Mário Luzeiro <mrluzeiro@xxxxx>]

Hi Cirilo,

> I have no plans for kicad and plugins to share code.
> As I wrote, plugins do not need to link to kicad or know anything about its internal data structures.

I understand that it don't need to be linked, but if you want to make a board exporter (eg: export a board to eagle) how does the plugin knows about the kicad structure of a board without knowing its internal structures?
I expect that the plugin receives some input data structure to process?


> For me that's ridiculous and would be a very bad thing for kicad. If people don't want
> to pull in the source tree while working on plugins that's not my problem. If they don't
> maintain their out of tree plugins if/when the API changes, that's not my problem. Why
> would I waste time working on imaginary problems created by other people who aren't
> contributing code to the official tree?

I was just asking to understand what was the approach that you are thinking to follow as there are different possible ways of doing it and it was not clear (for me) before.

Thanks!

Mario