X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Tue, 25 Aug 2015 15:49:36 -0400
Message-Id: <201508251949.t7PJnaJg031751@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <20150825213238.c7b0d9f599ca00b4e517e7d0@gmail.com>
	(geda-user AT delorie DOT com)
Subject: Re: [geda-user] speed-dial type buttons  (was:   Antifork)
References: <55D8D8B8 DOT 7050907 AT jump-ing DOT de>
	<20150822230549 DOT 3750 DOT qmail AT stuge DOT se>
	<55D9A5AE DOT 9090604 AT jump-ing DOT de>
	<C2FC0AF3-DFDB-4799-87F7-039614405DCD AT noqsi DOT com>
	<55D9BC06 DOT 9060106 AT iae DOT nl>
	<55D9C34A DOT 2090709 AT jump-ing DOT de>
	<C55E2A02-99F7-402C-953F-8E844004D61B AT noqsi DOT com>
	<201508232341 DOT t7NNfl9O012371 AT envy DOT delorie DOT com>
	<CF6D95DF-9FBF-48F6-8E68-458A2BC14CAF AT noqsi DOT com>
	<CAM2RGhS9QqDq2dZLwt7LfUFwQouCaX-SuxEu0U2ofNrxuttmhg AT mail DOT gmail DOT com>
	<55DA8231 DOT 4010904 AT mcmahill DOT net>
	<55DADE5A DOT 4020902 AT jump-ing DOT de>
	<CAM2RGhRd+JgbaxpM9wbqXYLWRrtc6FAw9ubwM42JFTytf8yEng AT mail DOT gmail DOT com>
	<55DB6A7C DOT 8090309 AT jump-ing DOT de>
	<CAM2RGhTkSRbWoQhPW6AcwMr3UFWbTXAPKnfD-2tUAC4psa1p-A AT mail DOT gmail DOT com>
	<55DB7F6A DOT 2050008 AT ecosensory DOT com>
	<20150825080001 DOT 5fc83c0223a8f3e52b5dd1bf AT gmail DOT com>
	<201508251626 DOT t7PGQeGY023950 AT envy DOT delorie DOT com> <20150825213238 DOT c7b0d9f599ca00b4e517e7d0 AT gmail 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
Precedence: bulk


In both cases there's a many-to-one relationship; one schematic can be
used for many purposes, and one pcb is made of many schematics.

So gschem would have to have many buttons, one for each purpose the
schematic is used for, but pcb would only need one - to collect the
things it needs.  PCB's File->Import does this; it knows how to use a
list of schematic pages or call out to a Makefile to get what *it*
needs.  A "getting started" button on gschem would need to assume that
the one schematic is sufficient for one pcb, or figure out how to ask
the user what other schematics are needed.  Also, not everyone starts
a pcb with the import - I prefer to lay out the board's boundaries and
physical size first, *then* import.

BOMs are trickier, because you need to know the set of schematics but
you also need to know the build-out of the board, i.e. which
configuration of parts is populated.  I typically use a script to
generate a BOM from schematics on a per-pcb basis, using attributes
from the schematic, but I can't see that working as a button in either
gschem or pcb.  Also, if your sch->pcb tool modifies any of the parts,
the BOM generator would need to know about that too.