X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
Date:	Fri, 1 Jan 2016 18:51:51 -0500
Message-Id:	<201601012351.u01Npphx017493@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	geda-user AT delorie DOT com
In-reply-to:	<624E6A69-62CE-4FCB-9D44-9FDF036254A3@sbcglobal.net>
	(geda-user AT delorie DOT com)
Subject:	Re: gEDA and it's future with Scheme & Guile was Re: [geda-user] Project leadership
References:	<CAM2RGhS4L-ch6FEcLtdSt0vA0BdQZvq+AuFDP+9ea7Ftd=AALg AT mail DOT gmail DOT com> <8444F816-17CE-4A56-A982-4A60DEDA72B8 AT noqsi DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1512300544550 DOT 9035 AT igor2priv> <87FC7D4C-157A-499E-8B93-97653D6A7C68 AT noqsi DOT com> <alpine DOT DEB DOT 2 DOT 11 DOT 1601012231450 DOT 1728 AT newt> <AE52C1DB-01A3-43FA-AE8E-68AD33F37180 AT noqsi DOT com> <624E6A69-62CE-4FCB-9D44-9FDF036254A3 AT sbcglobal DOT net>
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

> I would be interested to hear everyone's ideas on slotting and
> mechanisms for grouping/associating heterogenous symbols.

My thoughts on slotting/swapping haven't changed in a while.  IMHO...

We need a separate database that maps light symbols to heavy symbols.
That database can contain information about pin/gate swapping for
downstreams that need it.  Gnetlist (or some other go-between) will
have to combine that information plus the current "as-built" from
downstream to provide a new "should-be-built" to the downstream.

This *should* make it easier to do swapping at layout (which I think
is more appropriate anyway), reuse schematics for multiple downstreams
(by swapping databases), and various other things.

The down side is the need for back-annotation (either actually back,
or forward to as-builts) will be more of a pressing issue, as more of
the slotting info gets moved out of the schematics.  Plus the cost of
maintaining that database.

- Raw text -