X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-UW-Orig-Sender: fpm AT homer03 DOT u DOT washington DOT edu
Date: Fri, 8 Jan 2016 08:53:40 -0800 (PST)
From: "Frank Miles (fpm AT u DOT washington DOT edu) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject: Re: gEDA and it's future with Scheme & Guile was Re: [geda-user]
 Project leadership
In-Reply-To: <20160107175042.5e06aad2bf09818a8886d6f7@gmail.com>
Message-ID: <alpine.LRH.2.01.1601080823510.14656@homer03.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>
User-Agent: Alpine 2.01 (LRH 1217 2009-02-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-PMX-Version: 6.2.1.2493963, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.1.8.164216
X-PMX-Server: mxout23.cac.washington.edu
X-Uwash-Spam: Gauge=X, Probability=10%, Report='
 TO_IN_SUBJECT 0.5, HTML_00_01 0.05, HTML_00_10 0.05, SUPERLONG_LINE 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1400_1499 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, NO_URI_HTTPS 0, REFERENCES 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __FRAUD_BODY_WEBMAIL 0, __FRAUD_WEBMAIL 0, __HAS_FROM 0, __HAS_MSGID 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __REFERENCES 0, __SANE_MSGID 0, __SUBJ_ALPHA_END 0, __SUBJ_ALPHA_NEGATE 0, __TO_IN_SUBJECT 0, __TO_MALFORMED_2 0, __URI_NO_PATH 0, __URI_NO_WWW 0, __URI_NS , __USER_AGENT 0'
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




On Thu, 7 Jan 2016, Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:

>>>>  I can't use the
>>>> recommended direct PCB gschem-schematic-import method due to some special
>>>> schematic post-processing (mostly eliminating off-board parts/wiring, which I
>>>> want to have on the schematic),
>>>
>>> I attach graphical=1 to those to tell gnetlist that they don?t go into the netlist.
>>
>> That may work for whole parts, but doesn't work when particular pins/nodes need
>> to be separated from the board (thus the "/wiring").
>>
>>  	-F
>
> If you make one schematic for each circuit board it will work.
>
> It is possible to make a symbol matching connector output and put it higher than the circuit board(s) in the hierarchy. If you add a "source=board.sch" attribute you could get down into the hierarchy but symbol is not electrically connected to connector so for example DRC will not work for the whole circuit.

I really like a capable DRC.  Your recommendation would seem to make
both schematic and pcb DRCs problematic.  Making the circuitry much
harder to read by splitting a fairly simple input circuit into
multiple schematic pages seems very cumbersome and makes them harder
to understand (I'm particularly thinking of the techs who build and
sometimes have to repair these devices).

I have to wonder - what's so hard about getting pcb to understand
a circuit from a netlist?

 	-F