X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlemail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=n0iGcUz4zry0crh7z8Ifb6ZtktXkXKcl3dyjTWOHXTs=;
        b=Tqk/i9D01O42tuKPVBVCGUxTZ61QvIt1tgXMR1VFqRLKy6+2hViNMHwKBn8//2Jv12
         NYHUFbofqQ+9difZn5ajTk4t9wszn4luRZ+R5AxdmlCHHqbDQOVu+4tRv4S+m26xCsPR
         zS0Fa1LBohSCGlkfHrx/tuDQz4T+QxQexgfqXf86ciWllqUJZHqHxuwQ7ibYiGDVy/QJ
         ZTDOuRUtKofj5d67w8GBe0kq75FPmR5XKifFSdCyvh6m2eUal8D0RU4heeOU8qYWDz/7
         BvAITX48GgiRFIjQxEWBEO7MwJ2oHsW/sYHEglG41onHXsj8TOB1+tVCHhXmUk7Df8r4
         1NtQ==
MIME-Version: 1.0
X-Received: by 10.60.94.82 with SMTP id da18mr35119726oeb.40.1452619142095;
 Tue, 12 Jan 2016 09:19:02 -0800 (PST)
In-Reply-To: <alpine.LRH.2.01.1601120839240.16881@homer01.u.washington.edu>
References: <CAM2RGhS4L-ch6FEcLtdSt0vA0BdQZvq+AuFDP+9ea7Ftd=AALg AT mail DOT gmail DOT com>
	<8444F816-17CE-4A56-A982-4A60DEDA72B8 AT noqsi DOT com>
	<alpine DOT LRH DOT 2 DOT 01 DOT 1601040930510 DOT 18447 AT homer02 DOT u DOT washington DOT edu>
	<AF9F11C6-29A4-4558-85C8-973AB80BADFF AT noqsi DOT com>
	<CAC4O8c_ckyybeLDoV9oGM8cdH08goyqw6zG0eFn4dYdG_wchwg AT mail DOT gmail DOT com>
	<alpine DOT LRH DOT 2 DOT 01 DOT 1601060831110 DOT 31979 AT homer02 DOT u DOT washington DOT edu>
	<29B50AD8-DCD0-4048-B888-711C5D8E1E65 AT noqsi DOT com>
	<alpine DOT LRH DOT 2 DOT 01 DOT 1601070826250 DOT 1447 AT homer01 DOT u DOT washington DOT edu>
	<20160107175042 DOT 5e06aad2bf09818a8886d6f7 AT gmail DOT com>
	<alpine DOT LRH DOT 2 DOT 01 DOT 1601080823510 DOT 14656 AT homer03 DOT u DOT washington DOT edu>
	<20160108182822 DOT 3c4b5f2d183143b4a41680dd AT gmail DOT com>
	<alpine DOT LRH DOT 2 DOT 01 DOT 1601111041200 DOT 28725 AT homer02 DOT u DOT washington DOT edu>
	<201601111903 DOT u0BJ3A9a005050 AT envy DOT delorie DOT com>
	<5693FF30 DOT 1020208 AT iee DOT org>
	<alpine DOT LRH DOT 2 DOT 01 DOT 1601120839240 DOT 16881 AT homer01 DOT u DOT washington DOT edu>
Date: Tue, 12 Jan 2016 17:19:02 +0000
Message-ID: <CAJXU7q9OTdMpLMr6GbnCqLv_bHxjzOUsKgt-ovFdh5Qri9VUfQ@mail.gmail.com>
Subject: Re: [geda-user] Re: off-board parts/wiring
From: "Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: gEDA User Mailing List <geda-user AT delorie DOT com>
Content-Type: multipart/alternative; boundary=089e011603f6f567fa0529263fed
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

--089e011603f6f567fa0529263fed
Content-Type: text/plain; charset=UTF-8

On 12 Jan 2016 17:02, "Frank Miles (fpm AT u DOT washington DOT edu) [via
geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> wrote:
>

> Perhaps I'm confused.  I thought I had read that the netlist import was
> deprecated, and that the proper way of importing the netlist was through
> PCB:File/Import Schematics.  If netlist import is still equally valid,
> then please accept my apology for the needless noise.
>
>         -F

The import mechanism was added as a more integrated way of retrieving this
information, rather than relying on an external tool,  gsch2pcb to process
your existing design file and make edits. (This tool had to read and make
edits to the board files, so represented a barrier to format changes. This
was probably not the initial motivation of the new mechanism, but
represents a big plus point to its existence).

Underlying the mechanism is a netlist backend for gnetlist which describes
the components and nets of the design using a series of pcb action
commands. These are executed by pcb on the open design, and in turn update
the internal view of the netlist.

The "old" netlist format is not deprecated, although it does not convey all
of the information about parts etc.. (gsch2pcb managed that aspect based
upon a template file a separate gnetlist backend would populate with all
the parts of a given design).

Since gsch2pcb and associated netlist backends were in a separate code base
to pcb, this represented a compatibility problem if ever we changed things
with the file format. The new backend lives with PCB (iirc), so merely
relies on gnetlist keeping a stable scheme api and command line interface.

You might be interested to know that the update mechanism can be wired to
call a makefile (or other scripts?) to generate the required data, so it is
infact quite general. Only the "schematics" attributes are really assumed
to come from a simple gschem work flow.

At some point, I may update xgsch2pcb to use this new mechanism, rather
than gsch2pcb. It seems redundant to update gsch2pcb itself though.

Peter

--089e011603f6f567fa0529263fed
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"><br>
On 12 Jan 2016 17:02, &quot;Frank Miles (<a href=3D"mailto:fpm AT u DOT washington=
.edu">fpm AT u DOT washington DOT edu</a>) [via <a href=3D"mailto:geda-user AT delorie DOT co=
m">geda-user AT delorie DOT com</a>]&quot; &lt;<a href=3D"mailto:geda-user AT delorie=
.com">geda-user AT delorie DOT com</a>&gt; wrote:<br>
&gt;</p>
<p dir=3D"ltr">&gt; Perhaps I&#39;m confused.=C2=A0 I thought I had read th=
at the netlist import was<br>
&gt; deprecated, and that the proper way of importing the netlist was throu=
gh<br>
&gt; PCB:File/Import Schematics.=C2=A0 If netlist import is still equally v=
alid,<br>
&gt; then please accept my apology for the needless noise.<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 -F</p>
<p dir=3D"ltr">The import mechanism was added as a more integrated way of r=
etrieving this information, rather than relying on an external tool,=C2=A0 =
gsch2pcb to process your existing design file and make edits. (This tool ha=
d to read and make edits to the board files, so represented a barrier to fo=
rmat changes. This was probably not the initial motivation of the new mecha=
nism, but represents a big plus point to its existence).</p>
<p dir=3D"ltr">Underlying the mechanism is a netlist backend for gnetlist w=
hich describes the components and nets of the design using a series of pcb =
action commands. These are executed by pcb on the open design, and in turn =
update the internal view of the netlist.</p>
<p dir=3D"ltr">The &quot;old&quot; netlist format is not deprecated, althou=
gh it does not convey all of the information about parts etc.. (gsch2pcb ma=
naged that aspect based upon a template file a separate gnetlist backend wo=
uld populate with all the parts of a given design).</p>
<p dir=3D"ltr">Since gsch2pcb and associated netlist backends were in a sep=
arate code base to pcb, this represented a compatibility problem if ever we=
 changed things with the file format. The new backend lives with PCB (iirc)=
, so merely relies on gnetlist keeping a stable scheme api and command line=
 interface.<br></p>
<p dir=3D"ltr">You might be interested to know that the update mechanism ca=
n be wired to call a makefile (or other scripts?) to generate the required =
data, so it is infact quite general. Only the &quot;schematics&quot; attrib=
utes are really assumed to come from a simple gschem work flow.</p>
<p dir=3D"ltr">At some point, I may update xgsch2pcb to use this new mechan=
ism, rather than gsch2pcb. It seems redundant to update gsch2pcb itself tho=
ugh.</p>
<p dir=3D"ltr">Peter<br>
</p>

--089e011603f6f567fa0529263fed--