kicad-developers team mailing list archive
Mailing list archive
Re: P-Cad plug-in
On 6/26/2012 3:23 PM, Alexander Lunev wrote:
It was suggested to implement pcad2kicad converter as pcbnew plug-in. It is clear how to do this in the case of pcbnew. Even it is clear
how to do this in the case of eeschema. But it is not clear what to do with translation of P-Cad libraries (pcb and schematic libraries).
Now there are 4 different modes in pcad2kicad converter: converting pcb design files, converting pcb library files, converting sch design
files and converting sch library files. Considering the user interface how the converting libraries could be implemented applied to KiCad?
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
The next task on my list is to implement the Pcbnew module plugin as
part of the new file format work. That should resolve the module
library conversion issue. Using the Pcbnew s-expression format, modules
will be saved and loaded as individual files rather than a single file
with multiple modules as it currently stands. This will approximate the
SWEET design philosophy without inheritance and version tracking.
As for schematic component libraries, someone would need to write the
plugin for for loading and saving the existing libraries keeping in mind
the work Dick did on the SWEET library design. I'm not sure what the
best way to proceed with Eeschema would be. I have to sit down and try
to wrap my head around the work Dick has done and the legacy design and
try to come up with something reasonably sane. The Eeschema stuff may
have to be put off until I or someone else figures this out. It would
be nice to implement the new schematic file format but I have no idea
when I will have the time to work on the new Eeschema s-expression file
format code. Suffice it to say that it will not be soon.