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=_41EE8C0D-CA1D-476F-BC73-C9FC8611ED97"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [geda-user] Project leadership (design error in the core of gschem) X-Pgp-Agent: GPGMail 2.5.2 From: John Doty In-Reply-To: <20151230192636.fc377052d1b3314ceb5fd4c7@gmail.com> Date: Wed, 30 Dec 2015 11:54:51 -0700 Message-Id: References: <43CC8F96-6452-40FA-9DFB-E0983721C19C AT noqsi DOT com> <20151229094603 DOT 782092b57563336883546bfd AT gmail DOT com> <449C2A4A-814E-4858-ACB3-82807A80BE8A AT noqsi DOT com> <7C27D3F4-9CC2-46DB-BE88-77564F3FC0FC AT noqsi DOT com> <20151230192636 DOT fc377052d1b3314ceb5fd4c7 AT gmail 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=_41EE8C0D-CA1D-476F-BC73-C9FC8611ED97 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Dec 30, 2015, at 11:26 AM, Nicklas Karlsson = (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] = wrote: >>> And why gschem tries to understand slotting in the first place, and = doesn't leave it for the netlister? >>=20 >> I think that=92s because the concept of forward annotation to an = as-built schematic was not on the table when it was implemented. The = developers thought that users would need to see pin numbers in the = source schematics. I suppose there are many who will still want this = even after we construct a good way to make as-built schematics. >>=20 >> John Doty Noqsi Aerospace, Ltd. >> http://www.noqsi.com/ >> jpd AT noqsi DOT com >=20 > I have been thinking about an annotation mechanism so that it possible = to annotate decisions made later during design flow without changing the = original schematics but it may also add confusion. I figure you can always copy the annotated files to the source if that=92s= a problem. When I went through the exercise of partially reconstructing = schematics from an Osmond netlist a few months ago, I put the result in = a separate git branch as source. Most people on big projects who use my schematics are reading the PDF = =93user=92s manual=94. I generate that by incorporating = forward-annotated PDF schematics and other design information into a = LaTeX document. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com --Apple-Mail=_41EE8C0D-CA1D-476F-BC73-C9FC8611ED97 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 iQIcBAEBCgAGBQJWhCh7AAoJEF1Aj/0UKykRPjoP/R/6pBGzgaiqgBIZhTa58WhG 0yI5jylvRf0O2e+A9Dxr1S5RRCMja/JCCZGklB0E5Ig4C+X3lIgUubMHUaH30vyM YIAq9DIETePZf3Xq9Xeane62K5bXOZdcV+GWVteq3bus1Sx+1R6eMb9GXaDc4dP2 Eu1tkAsoIh6OD8bkczrJhxTocIrp/8ZUidZBa+y1J+9pbrjkA1tAjKKNH/orClQm 9didRoJTq+YOUi1pW9PvOIUtvieeT9vT/0lA3AI9zRY4QEyj7Nsw4vilw0OUCRrA PMGe6UJCssGJ5D9ypbsLWb9UQiyMjx6OLeB4jP3J/kK3WoWzmzZG/HLl/EiqeHLB ZG3wjTQId5v96epRvY7mN/Qw45A9sWZteWVfRcClekWbcVseI8QYVAvSjVhBmFso s/Bz0mEQaofelPmKf7RKe0dcrx0S9OVcj/83VF0uwmNqU7YktfXRxewA6TuKyK8q JuqEvfOby44rW16s7fmbePYJyIfEzx6ZuPTnQIZIDF/85Gp4ap380L5Pbsm45vqb jfUjVJD4gSHwOHWndF/2cthb2siB7Exa7ZNL2sEXRZnXkRYSIME1m9WOtFyOpyEC ViSL9APEHa3W5GJgPPGzPdEmkkfbx1N45y10jcdG7iqneHIRtqELLDz9MDUhRoRC d37eM37TvdhJ/VWKOjy9 =/RiX -----END PGP SIGNATURE----- --Apple-Mail=_41EE8C0D-CA1D-476F-BC73-C9FC8611ED97--