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

[John Doty <jpd-at-NOSPAMwispertel_dot_net>]

On May 29, 2007, at 1:43 PM, al davis wrote:

> On Tuesday 29 May 2007, Steve Meier wrote:
>> To answer the following critique:
>>> "gnetlist" provides a one way mechanism from gschem out,
>>> essentially based on something like a plug-in for the
>>> output format.
>>
>> I have a modified version of gnetlist that I have been
>> calling backnet.
>>
>> backnet uses a front end scheme file to construct the libgeda
>> data structures from something. Currently I have a script for
>> importing pads netlists.
>>
>> backnet also can run an intermediate scheme script to then
>> manipulates the libgeda data structures. Again the script
>> that I have imports an eco file from pads.
>
> cool...

Indeed.

>
> What you are doing differs from my original VHDL proposal in one
> significant way:  The choice of the middle format.

And I see two significant advantages here:

1. This preserves our investment in gnetlist back ends (and I'm not  
talking just about the code). We keep a flow that works well.

2. Guile data structures are themselves flexible and completely  
extensible. They are easy to store portably in files. This could give  
us a *neutral* file format for design data interchange. This seems  
much better to me than adapting a drawing, layout, or simulation  
format to cover all of these bases. Use a format simply designed for  
representing data.

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