X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-TCPREMOTEIP: 207.224.51.38
X-Authenticated-UID: jpd AT noqsi DOT com
Content-Type: multipart/signed; boundary="Apple-Mail=_BC50807E-6B9E-4EA9-84BA-B5167AEECAD1"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: [geda-user] Pin mapping (separate symbols from mappings)
X-Pgp-Agent: GPGMail 2.5.2
From: John Doty <jpd AT noqsi DOT com>
In-Reply-To: <201510191647.t9JGlu4j024585@envy.delorie.com>
Date: Mon, 19 Oct 2015 12:28:14 -0600
Message-Id: <041FF42A-691F-4E6B-9DEB-8C6B3C2F3E53@noqsi.com>
References: <20151018204010 DOT 9cce6a231dcc296256e187bd AT gmail DOT com> <201510181843 DOT t9IIhmWo025346 AT envy DOT delorie DOT com> <20151018234424 DOT c0551dad9bef0859130239d9 AT gmail DOT com> <36B94694-F2AC-4A75-A8EB-40A1CE9A534C AT noqsi DOT com> <201510182225 DOT t9IMPkxK032763 AT envy DOT delorie DOT com> <20151019003814 DOT f62620bf0fec77e65104c105 AT gmail DOT com> <BED51F9A-F6FF-4A23-B18B-C2EC8BB9DAB6 AT noqsi DOT com> <201510190242 DOT t9J2gl7w009345 AT envy DOT delorie DOT com> <20151019092555 DOT 46eed4540c2d2044bbeab878 AT gmail DOT com> <1A419AED-FCCA-4B1F-8589-912435534E2E AT noqsi DOT com> <201510191647 DOT t9JGlu4j024585 AT envy DOT delorie DOT com>
To: geda-user AT delorie DOT com
X-Mailer: Apple Mail (2.1878.6)
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


--Apple-Mail=_BC50807E-6B9E-4EA9-84BA-B5167AEECAD1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Oct 19, 2015, at 10:47 AM, DJ Delorie <dj AT delorie DOT com> wrote:

>=20
>> And you need a way to distinguish them.
>=20
> I think we're underestimating the importance (and complexity) of that.

I think you want something foolproof. That desire will drive a great =
deal of complexity, and I don=92t think it=92s possible without =
seriously getting in the way of user needs.

>=20
>> although slotting is arguably a messy feature rather than a clean
>> fundamental capability.
>=20
> So... what if we dumped slotting?

A lot of current projects would break.

>  What would schematics look like
> then?  Do we assume/require that the user will create a schematic with
> a separate refdes for each gate in a package?

Unless you make a kit which is fundamentally alien to the way that =
geda-gaf works, I think this is necessary.

>  That, of course means
> we need to set some expectation of what <downstream>'s package refdes
> would look like,

We=92re talking about abstract schematics, right? Consider a generic =
Sallen-Key filter as given at: =
https://en.wikipedia.org/wiki/Sallen%E2%80%93Key_topology#/media/File:Sall=
en-Key_Lowpass_General.svg. You have R1, R2, C1, C2. Do you expect those =
to carry over into the final as-built design?

> but it would mean that refdes is unique enough...
>=20
> ... except for cases where the user splits one package up into
> multiple symbols because of complexity, like breaking up an MCU or
> splitting out power pins.
>=20
> Are there cases where a package contains two identical copies of
> something complex enough to each be broken into separate symbols?

Microcontroller I/O ports, FPGA I/O banks. Probably other things. I =
don=92t trust the limits of my imagination, and you shouldn=92t either.

>=20
> And the user still needs some mechanism to connect up power/ground
> pins on multi-gate packages.
>=20
>> I do believe we need a way to override pin attributes in instances.
>=20
> +1
>=20
>> Embed the symbol and edit?
>=20
> Perhaps this is the right solution for an as-built anyway, as it locks
> in the symbols it was built with.
>=20

John Doty              Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com



--Apple-Mail=_BC50807E-6B9E-4EA9-84BA-B5167AEECAD1
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJWJTY+AAoJEF1Aj/0UKykRpdcP/ioPtnlbgNDvqStF3cxTROfc
5zvHyQgcnJDoGnBZdv7mUXmo1ai21qh30ZAvqGy5om2wAqb3PqcLfwbjLwbuIkhA
N1YQr45Z0T/P+NLwWnS1sf7AmkFlxHlrtw81JZCkS0azkgh6S1kAOKA7t2pMSCoV
S9XSfflzSwoHFx5vvR8j6Ka3rOdDqIjProXDMB1izMWtg3Kt7bUJCNbW/0sSbWdM
7t6jqIT4TCHet+LgFA+qWnV5vvHfhdjjS7wgYdvNVNsm4yZzEt1sNcv0WbEGULYj
/N+KDvr2orTMbQ9mLi4L0PM+EI6SxKHTFwJO61fmb5cAliKxlNlrwJEqPltujC1P
eMlJxyQu+BRxAoYJ1csGFl8paxIGkNlbkOqVxUtS3vnzw+EwXkP4zp2h+6VrCg8F
CgLJqDMMOCdbYzKA91mYeHD5QurtbdJEG54bWOurdkAXElpgFFF4SfWzNJrWCWq8
Fi3RPfWCd1rENMudY16z0sorDti95oT5OXVX91a27rWe+WXE1G1Bzj+k+7ocPrOP
SNGNBPjI6AnT0sXbVhf7SKynPVzzAOK4cAtbax0rUdUfjaChUnaFqhq3/20nhpPl
tk+O6yomt71MHsXsz/tcU4O/uh17I75vWo9AQPgm+R+5m6RNj7Enr9iUVQ0kGtOy
FiAZtQnVE3rdTTnpmw4k
=oWiO
-----END PGP SIGNATURE-----

--Apple-Mail=_BC50807E-6B9E-4EA9-84BA-B5167AEECAD1--