delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2016/01/13/14:08:37

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=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type;
bh=aXd+ePzyoXRkg0d3zir4JF3r1Vo3cEEilmMngD9+JbU=;
b=bvINjchuhPoc/B0T03OOzL4Pwc+frkaIvC3/NTv6+jPpa9PjyyPPFmEkW4o0C++Xl+
J64v1hU8hw3J+ivhytc34lrYu8lVxOaxfCosUGkodrIpWW0BotQVNhxEQMXVOkLjZFxt
eUtuITZN50mka7rCGcdMydTpH/wAa7+gZ4A7/fHL+rvVpTMKZxlL0bBuFXXwsb6KsUUB
BXL6tv283K9qIH+0EmdyCSBE0W3z54bh7asnVoMUaU6/X0r14WHgslk/6lGqaMrtr4jy
lYLuBJC2UAg6NNel1+oTgabQ83DzFUmY8gl4qYfbG51v5JWpi3+LKPXY7gYnbWG48JnP
mqig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:content-type;
bh=aXd+ePzyoXRkg0d3zir4JF3r1Vo3cEEilmMngD9+JbU=;
b=bKI7UTSxz+HPqZ2vGi1+z0h9gpUFt224SC2ISn4Ea2t3vbGjd5v0XTU1o6tnDVH0mN
G0zW4EUQhBiuv81yVEfWDY9zqT+nQckQUIv5wDlC2l8eEnUNCD1bLlD86RGAMcT5FAfV
rwl/eOjlkBZoWbL5j66mswqD0iLSB8a1ZQMp+20dEmVd1I/RBZuykyajoQb+n5eAKvqF
p1PZsyoK/Jme+c6Y4Km4+7OpeqNHYDx0manqpvdJM+5DZRd5O/CQQkyvSlBvgoprB9oj
f2yKBwQ5A4skSjP7kUFBcPKLADe8T0ZDMmBYylogV+3KHNwxXP1y+jomg2FBOO9ebAfe
pNrg==
X-Gm-Message-State: ALoCoQmBYr2WQOXmE06Uomil+jYSnkBtSqdiC9LoVssHGZ4Fvg3Qwu53U80Mi1FIiD29SsbIujn3i6h4Nt5Lct2JbJbEKWiv7Q==
MIME-Version: 1.0
X-Received: by 10.194.173.233 with SMTP id bn9mr147238402wjc.1.1452712017985;
Wed, 13 Jan 2016 11:06:57 -0800 (PST)
In-Reply-To: <56965E3B.2070409@iee.org>
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>
<CAJXU7q9OTdMpLMr6GbnCqLv_bHxjzOUsKgt-ovFdh5Qri9VUfQ AT mail DOT gmail DOT com>
<56965E3B DOT 2070409 AT iee DOT org>
Date: Wed, 13 Jan 2016 10:06:57 -0900
Message-ID: <CAC4O8c-=H2vxMbbVrty3BfATcY5y625TH6BDQu0FqZGWQ=3uEQ@mail.gmail.com>
Subject: Re: [geda-user] Re: off-board parts/wiring
From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
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

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

On Wed, Jan 13, 2016 at 5:24 AM, M. J. Everitt (m DOT j DOT everitt AT iee DOT org) [via
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:

> On 12/01/16 17:19, Peter Clifton (petercjclifton AT googlemail DOT com) [via
> geda-user AT delorie DOT com] wrote:
>
>
> 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
>
> I confess to never using the Import Schematics, probably because its only
> just appeared in the builds I have ready access to. I have never had any
> problems with the gsch2pcb workflow, like much of geda-gaf, it's quirky,
> but it works, and and you soon figure out how to make it do what is
> necessary.
>

It took me a long time to get around to trying it as well, for about the
same reason.  It's worth it though, especially if you find yourself making
a lot of small changes on the gschem side and routing them incrementally.

Britton

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Jan 13, 2016 at 5:24 AM, M. J. Everitt (<a href=3D"mailto:m.j.e=
veritt AT iee DOT org">m DOT j DOT everitt AT iee DOT org</a>) [via <a href=3D"mailto:geda-user AT d=
elorie.com">geda-user AT delorie DOT com</a>] <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    On 12/01/16 17:19, Peter Clifton (<a href=3D"mailto:petercjclifton AT goog=
lemail.com" target=3D"_blank">petercjclifton AT googlemail DOT com</a>)
    [via <a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">geda-us=
er AT delorie DOT com</a>] wrote:<br>
    <blockquote type=3D"cite">
      <p dir=3D"ltr"><br>
        On 12 Jan 2016 17:02, &quot;Frank Miles (<a href=3D"mailto:fpm AT u DOT wa=
shington.edu" target=3D"_blank">fpm AT u DOT washington DOT edu</a>)
        [via <a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">ged=
a-user AT delorie DOT com</a>]&quot;
        &lt;<a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">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 r=
ead that
        the netlist import was<br>
        &gt; deprecated, and that the proper way of importing the
        netlist was through<br>
        &gt; PCB:File/Import Schematics.=C2=A0 If netlist import is still
        equally valid,<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 retrieving this information, rather than relying on an
        external tool,=C2=A0 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).</p>
      <p dir=3D"ltr">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.</p>
      <p dir=3D"ltr">The &quot;old&quot; 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).</p>
      <p dir=3D"ltr">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.<br>
      </p>
      <p dir=3D"ltr">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 &quot;schematics&quot; attributes are really assumed to come fr=
om a
        simple gschem work flow.</p>
      <p dir=3D"ltr">At some point, I may update xgsch2pcb to use this new
        mechanism, rather than gsch2pcb. It seems redundant to update
        gsch2pcb itself though.</p>
      <p dir=3D"ltr">Peter<br>
      </p>
    </blockquote>
    I confess to never using the Import Schematics, probably because its
    only just appeared in the builds I have ready access to. I have
    never had any problems with the gsch2pcb workflow, like much of
    geda-gaf, it&#39;s quirky, but it works, and and you soon figure out ho=
w
    to make it do what is necessary.<br>
  </div>

</blockquote></div><br></div><div class=3D"gmail_extra" style=3D"">It took =
me a long time to get around to trying it as well, for about the same reaso=
n.=C2=A0 It&#39;s worth it though, especially if you find yourself making a=
 lot of small changes on the gschem side and routing them incrementally.</d=
iv><div class=3D"gmail_extra" style=3D""><br></div><div class=3D"gmail_extr=
a" style=3D"">Britton</div><div class=3D"gmail_extra"><br></div></div>

--089e0122f088cb57a805293bdff4--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019