I have a version of gnetlist which allows you to read in a set of schematics and generate a netlist or just read in a netlist. You can then run one or more scripts to manipulate the internal data. Finally you can run a back end script to export the data structure. There are a couple of issues (bugs) one being that since I am almost exclusively working hierarchically I seem to only support only one top level schematic, so a schematic with multiple pages has to have a top level and then use symbols with embedded schematics to include the other pages. Steve Meier On Wed, 2008-10-22 at 12:39 -0600, John Doty wrote: > On Oct 22, 2008, at 11:58 AM, al davis wrote: > > > On Wednesday 22 October 2008, John Doty wrote: > >> (3) write a gnetlist back end (not as hard as it looks): > >> gnetlist is effectively the tool for libgeda scripting. > > > > sorry .... he needs to go the other way. > > > Hmm. Where's the barrier to mucking with the data structures and > writing them back out from gnetlist? > > John Doty Noqsi Aerospace, Ltd. > http://www.noqsi.com/ > jpd@xxxxxxxxx > > > > > _______________________________________________ > geda-user mailing list > geda-user@xxxxxxxxxxxxxx > http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Attachment:
Netlist Users Guide V1.odt
Description: application/vnd.oasis.opendocument.text
Attachment:
guile_interface_rev0.04.odt
Description: application/vnd.oasis.opendocument.text
_______________________________________________ geda-user mailing list geda-user@xxxxxxxxxxxxxx http://www.seul.org/cgi-bin/mailman/listinfo/geda-user