X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f X-Recipient: geda-help AT delorie DOT com Date: Fri, 4 Sep 2020 15:11:40 +0200 (CEST) From: Roland Lutz To: "Roger Traylor (traylor AT engr DOT orst DOT edu) [via geda-help AT delorie DOT com]" Subject: Re: [geda-help] Linux In-Reply-To: <0839C430-BE38-4A0C-AD1A-0DD9F75A8DDD@noqsi.com> Message-ID: References: <20200829221451 DOT GA2565 AT newvzh DOT lokolhoz> <664de6c2-ad96-8298-1b64-ad550acfca64 AT k4gvo DOT com> <20200901193434 DOT GB19839 AT newvzh DOT lokolhoz> <20200902141116 DOT GA2911 AT newvzh DOT lokolhoz> <20200902165424 DOT GB2911 AT newvzh DOT lokolhoz> <333FD0E9-238C-445F-AEE4-850B0EA19A88 AT ece DOT orst DOT edu> <2A687A4D-3219-431E-8866-2D11C2418C81 AT noqsi DOT com> <0839C430-BE38-4A0C-AD1A-0DD9F75A8DDD AT noqsi DOT com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="8323329-438431161-1599225100=:11981" Reply-To: geda-help AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-help 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. --8323329-438431161-1599225100=:11981 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT On Thu, 3 Sep 2020, John Doty wrote: > On Sep 3, 2020, at 6:01 PM, Roland Lutz wrote: > > On Wed, 2 Sep 2020, John Doty wrote: > > > I favor Lepton [because] it’s agnostic about which layout program > > > you use: it has no favored layout component. […] > > > The layout people I work with all have different favorite tools, so > > > decoupling schematic entry and layout is very important to me. > > > > This is absolutely the same for gEDA/gaf. > > No, gEDA/gaf is joined to PCB. The tail wags the dog. gEDA/gaf supports a variety of layout programs via netlister backends, some of which you contributed yourself. There's even backends for SPICE and cascade simulation which doesn't involve layout at all. >> Xorn is an internal component; you don't have to understand or even >> consciously interact with it in any way.  (But even if you did, it's >> not more complicated than the Scheme API.) > > Except if you’re writing back ends, you do. There's a Scheme and a Python variant of the gnetlist API. You can use either to write a backend. > I’ve done things in Python. It wasn’t the problem. The problem was to > figure out the API. Let's stay at the example of the Osmond PCB backend. It accesses the netlist in the following ways: - netlist.packages (the packages in the netlist) - netlist.nets (the nets in the netlist) - package.refdes (the refdes of the package) - package.get_attribute('footprint', 'unknown') (gets the "footprint" attribute of the package, with "unknown" as the default) - net.name (the name of the net) - net.connections (a list of pins connected to the net) - pin.number (the pinnumber) - pin.package (the package to which the pin belongs) What about that do you consider hard to figure out? Roland --8323329-438431161-1599225100=:11981--