Re: gEDA-dev: gnetlist as one way path?

[John Doty <jpd-at-NOSPAMwispertel_dot_net>]

On May 31, 2007, at 7:08 PM, Steve Meier wrote:

> Uhm, this isn't ment to be a translator it is ment to be a netlist
> manipulator. Translation is a bonus.

Translation from a database to a netlist is sensibly a separate  
program. But then the ability to merge the data and create a combined  
netlist is key.

>
> I build tools that I need to get something done.

Me too. But we can put our stuff together.

>
> Hence the imputous to backnet was to be able to generate a netlist  
> for a
> project that has 28 pages of schematics. Some the of the pages get  
> used
> multiple times and this includes the useage of hierarchical buses.
>
> At layout time, as expected, efficient trace routing required swapping
> io pins thus causing the actual netlist to not reflect the schematic
> netlist. Then we discovered a few schematic issues which required
> regenerating the netlist. At this time I can't import the layout  
> program
> eco files back into the schematic so I decided to use it to directly
> update the schematic.
>
> Hence, the middle scheme routine in backnet.
>
> For the record backnet and my netlister both have very few lines code.
> The vast majority of the code is in my version of libgeda.

Sounds very nice. What would it take to get your version of libgeda  
into the gEDA mainstream?

John Doty              Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd@noqsi.com




_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev