X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Subject: Re: [geda-user] Re: off-board parts/wiring
To: geda-user AT delorie DOT com
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>
From: "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>
Message-ID: <56965E3B.2070409@iee.org>
Date: Wed, 13 Jan 2016 14:24:59 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <CAJXU7q9OTdMpLMr6GbnCqLv_bHxjzOUsKgt-ovFdh5Qri9VUfQ@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------000606080902020605030507"
X-Provags-ID: V03:K0:mie7bNwjdzRL967Ukx8t1cXfhub0DWXdl70w9Q+HENqfOTy3c7b
 hHcHthU07/l891P02NSK/D7YXZNAeYGGWgqWfHPRNrDs0XC9gt4aNI+ujFxtfGG/qKbxMdH
 0p4FfiUWVBcLk2iwgLor01zDaduSgsy6efkeBjMazET11UkV9tuJFUuZ3d74vMwjLwwnOe5
 yz68UKNEq1kGXkJF3Fu5w==
X-UI-Out-Filterresults: notjunk:1;V01:K0:MVVEj2qwMzA=:+9hFzuTDP3u90kWyze9WxV
 VIMI2o6Ezh76Dn+Pruqs/1eONju4+WYxWE3lgJFILT46C/7CJrUoQuuei6DhAI9MpGJF0cUoV
 mNy2b3eQgYOuKgA3DwJWV5F51us9Ni8rpkY2rB4CrpIPMhWZSLFTInUx2R1tgZIYOj6fxH93p
 Z6creeukEFn2bJQRu4QqOuNbnSVNHJXa1lmWW9f451/W6CgtdRSYKUIZj/f93xYxSzdiZmJC/
 JeGi1cuhbD83DbWZLIZjPWh0fJGhzSGYyiYyfVFriGzHlaWtwBCk0h+5zxcDOVhjm5JopC2q/
 Cy84oAuXQjNoq7o74KqwbWy9Fz7JBmd8LRNFA0tUCj03jhGec/idayZN7m6ACZWfsvcO5fUoj
 kxdcTc+dKFxh5nQCID5dtXDEmbpbM1BIyoU9sLr5UoJsM5LgFHoRB8lqE7w4cFxxOvzoffT3H
 79X4azZ117c/0powXTRDfZkJwzsm7BACJU2nCmamzLv9y+koc3cL1eJqFckrSr4tqp69kGPdu
 ruUfJW8t/k69gax+8Id0XLvHNemPmyOfNFoQOidzRyKGr6i9WeHKr8EpDV38EU3BjM2ea8Z6U
 SzubU6zzbsh2jUtt539Ek8TlsrA/8tqrHL5IFRNiqXGvTCBdO4x0I4xWCVCrg8oVJ9XeCzcD2
 K12niXzcTEvtII+Jc4eYHcpHWJSLZDGEiP6zH5ugbQIGGc97ALluwCMeNoLehvPWAcVVXrMm8
 z9c4fSe3sID3JwEJYD4llO/H1Xwvua2NLyXz/VNlyRe+lHqGDBPXq9A/NLqThJWUj/kASG9HN
 5W+Gs7HVojo/W9GNxoh402x/7HSFQ==
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 is a multi-part message in MIME format.
--------------000606080902020605030507
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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
> <mailto:fpm AT u DOT washington DOT edu>) [via geda-user AT delorie DOT com
> <mailto:geda-user AT delorie DOT com>]" <geda-user AT delorie DOT com
> <mailto: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.

--------------000606080902020605030507
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    On 12/01/16 17:19, Peter Clifton (<a class="moz-txt-link-abbreviated" href="mailto:petercjclifton AT googlemail DOT com">petercjclifton AT googlemail DOT com</a>)
    [via <a class="moz-txt-link-abbreviated" href="mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>] wrote:<br>
    <blockquote
cite="mid:CAJXU7q9OTdMpLMr6GbnCqLv_bHxjzOUsKgt-ovFdh5Qri9VUfQ AT mail DOT gmail DOT com"
      type="cite">
      <p dir="ltr"><br>
        On 12 Jan 2016 17:02, "Frank Miles (<a moz-do-not-send="true"
          href="mailto:fpm AT u DOT washington DOT edu">fpm AT u DOT washington DOT edu</a>)
        [via <a moz-do-not-send="true"
          href="mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>]"
        &lt;<a moz-do-not-send="true"
          href="mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>&gt;
        wrote:<br>
        &gt;</p>
      <p dir="ltr">&gt; Perhaps I'm confused.  I thought I had read 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.  If netlist import is still
        equally valid,<br>
        &gt; then please accept my apology for the needless noise.<br>
        &gt;<br>
        &gt;         -F</p>
      <p dir="ltr">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).</p>
      <p dir="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="ltr">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).</p>
      <p dir="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="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 "schematics" attributes are really assumed to come from a
        simple gschem work flow.</p>
      <p dir="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="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's quirky, but it works, and and you soon figure out how
    to make it do what is necessary.<br>
  </body>
</html>

--------------000606080902020605030507--