X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Thu, 14 Jan 2016 04:00:26 +0100 (CET)
X-X-Sender: igor2 AT igor2priv
To: "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>
X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From: gedau AT igor2 DOT repo DOT hu
Subject: Re: [geda-user] Re: off-board parts/wiring
In-Reply-To: <5696C7F4.2030003@iee.org>
Message-ID: <alpine.DEB.2.00.1601140358230.9035@igor2priv>
References: <CAM2RGhS4L-ch6FEcLtdSt0vA0BdQZvq+AuFDP+9ea7Ftd=AALg AT mail DOT gmail DOT com> <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> <CAC4O8c-=H2vxMbbVrty3BfATcY5y625TH6BDQu0FqZGWQ=3uEQ AT mail DOT gmail DOT com> <5696C7F4 DOT 2030003 AT iee DOT org>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-233255500-1452740426=:9035"
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

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-233255500-1452740426=:9035
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE


On Wed, 13 Jan 2016, M. J. Everitt (m DOT j DOT everitt AT iee DOT org) [via geda-user AT del=
orie.com] wrote:

>
>On 13/01/2016 7:06 pm, Britton Kerin (britton DOT kerin AT gmail DOT com) [via
>geda-user AT delorie DOT com] wrote:
>
>
>      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.=C2=A0 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.=C2=A0 If
>                  netlist import is still equally valid,
>                  > then please accept my apology for the
>                  needless noise.
>                  >
>                  > =C2=A0 =C2=A0 =C2=A0 =C2=A0 -F
>
>                  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).
>
>                  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.=C2=A0 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
>
>I'm assuming we're still waiting for Peter's code to back-annotate changes
>from the pcb layout editor to the schematic editor?! Otherwise, netlist
>changes aren't usually too painful. It's a greater pain updating component
>values, doing a new BOM export, and merging the changes to my spreadsheet =
!!
>:P

Note: I already have a working mechanism for back annotation in pcb-rnd=20
and a temporary fork of gschem:

https://archive.org/details/pcb-rnd-back-annotation


--0-233255500-1452740426=:9035--