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
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 <jpd AT noqsi DOT com>
In-Reply-To:	<CAM2RGhQfQqhrHCyShXagCM2Fa-+UyLTtLwxmHhKu92ydV_sSaQ@mail.gmail.com>
Date:	Thu, 31 Dec 2015 17:16:13 -0700
Message-Id:	<E9FEC0A3-ADAA-4DFB-A0BE-63176D053122@noqsi.com>
References:	<CAJXU7q_3XwthnN_8mp7B+-ShHeK+=7J=54ZavKBUG3S3bSKp2A AT mail DOT gmail DOT com> <CANEvwqiM7CKG+WpDRpG4L=HsmSEZ32=CBDyUhuk3ks-SNedL2Q AT mail DOT gmail DOT com> <43CC8F96-6452-40FA-9DFB-E0983721C19C AT noqsi DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1512290406210 DOT 9035 AT igor2priv> <20151229094603 DOT 782092b57563336883546bfd AT gmail DOT com> <CAM2RGhQ363RydhBJKMnNX5sLOkD1K4qVwb-PPwov3MT3D6MfdQ AT mail DOT gmail DOT com> <449C2A4A-814E-4858-ACB3-82807A80BE8A AT noqsi DOT com> <CAM2RGhQD1b0NKLWNYyB-m1whgYJZeEH9syzSs4OZt+22D5hooA AT mail DOT gmail DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1512300441390 DOT 9035 AT igor2priv> <E8E70657-A89A-4F51-B779-C24E029ABECA AT noqsi DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1512300611420 DOT 9035 AT igor2priv> <C3D7084C-1A24-4266-806D-C337CFA17322 AT noqsi DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1512300716090 DOT 9035 AT igor2priv> <E5C6D693-D7F1-41B0-934F-CBAFD710D67E AT noqsi DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1512300804420 DOT 9035 AT igor2priv> <6645DDA7-7371-4E11-8B8D-82279DCC7C41 AT noqsi DOT com> <CAM2RGhQfQqhrHCyShXagCM2Fa-+UyLTtLwxmHhKu92ydV_sSaQ AT mail DOT 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

--Apple-Mail=_88EB09B3-32A6-46DC-B5E4-2293C48B2C65
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Dec 31, 2015, at 4:53 PM, Evan Foss (evanfoss AT gmail DOT com) [via =
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:

> On Wed, Dec 30, 2015 at 7:34 AM, John Doty <jpd AT noqsi DOT com> wrote:
>>=20
>> On Dec 30, 2015, at 12:17 AM, gedau AT igor2 DOT repo DOT hu wrote:
>>=20
>>>=20
>>>=20
>>> On Tue, 29 Dec 2015, John Doty wrote:
>>>=20
>>>>=20
>>>> On Dec 29, 2015, at 11:22 PM, gedau AT igor2 DOT repo DOT hu wrote:
>>>>=20
>>>>>=20
>>>>>=20
>>>>> On Tue, 29 Dec 2015, John Doty wrote:
>>>>>=20
>>>>>>=20
>>>>>> On Dec 29, 2015, at 10:29 PM, gedau AT igor2 DOT repo DOT hu wrote:
>>>>>>=20
>>>>>>>>=20
>>>>>>>> A common netlist/bom format with a canonical form (so =
equivalent netlists would be identical) would be a useful intermediate.
>>>>>>>=20
>>>>>>> Could work. To me, the current patch format is much cleaner. I =
already have fully working code both in pcb-rnd and gschem. If you =
implement an alternative solution that is at least as capable, let me =
know.
>>>>>>=20
>>>>>> I?m not saying get rid of your patch format. But you took a =
shortcut generally not available by having pcb make the patch directly.
>>>>>=20
>>>>> False. I did make a shortcut, but on a totally different level of =
abstraction.
>>>>=20
>>>> Only available to the geda-gaf->pcb flow.
>>>=20
>>> Nope, it's available in the pcb->geda-gaf flow. Not due to the =
format, not due to the shortcut. Only because I did't implement it for =
anything else.
>>>=20
>>> Please provide your reasoning why anything else couldn't emit a =
similar format!
>>=20
>> Not directly from a tool whose code you can=92t modify. Indirectly =
through through additional scripts, of course, which is my proposal.
>>=20
>> How would you implement this for Osmond PCB?
>=20
> I have no idea as I have no idea about Osmond. I assume some Osmond
> user will provide documentation on the Osmond output format that will
> enable a plugin or translation utility to be created. Simply because
> Osmond is not supported does not mean we don't implement this. It just
> means Osmond users won't in the short term be able to use a feature.
> Their already existing flow will still work and I don't see a problem
> with that.

I guess I wasn=92t clear. There is common infrastructure for creating =
the patch file that Igor has hard-wired into his pcb. An Osmond flow =
cannot use this. On the other hand, if that common part was a separate =
tool using a canonical netlist format, every flow involving a layout =
program that can export an as-built netlist could use it. All you=92d =
need is a translator from each tool=92s export format to the canonical =
format. Igor has a short cut for pcb, but that short cut is not =
available to any other flow.

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



--Apple-Mail=_88EB09B3-32A6-46DC-B5E4-2293C48B2C65
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

iQIcBAEBCgAGBQJWhcVOAAoJEF1Aj/0UKykRHSsP/2QYe8esuEDzDGPUpTaho6Lg
Rq7yxVIzTEeOOfRnQNdL0gzWeC2VnepE8Shvj+xF4URProMqgrjnHDCBZFbFmdBd
Zh1ny/ysxIM/GgB0rM2llPGgry9cDzYS1sPU+0/lHliR6a0I7mxQWkMmtZUJwXxb
DYGG2Gyw9AE3ipZ7cNrKo46kcILIXd6oclrngOXNTWVbeWbFUfEaqU6//LIWODBq
4DBpk9zs65lHyQ6Y5FskPIO8AAyzN0OTsRnlCSMsnRUFRrvIf8UaZBRdp2XKbJva
/eIwM6xAYxkVSWvySj/XAFEBf2xtEk/0Cd8cGust2gb3ote5CrvlnVRJtiWqnuB7
UpYPpPrjk5BBYtiSK+OYKrzvSpWsryvn5980S+c/2P9HspoVuo9T1mbe3W5Uq5IS
ImDC6GNXlrDQxSphfqexts/73I9amQZm7CsXlIQNh+akjz7nRyH/nMTCkUoj9Vkq
R3aUtJEAm7CgO+3Oe97hiCrroNj6vr4Q6oIbVEF9NFqJNHxbxQlfkhG5OCOtQUa5
sEBVq8C16ywYBGCBSurTJYTkKffI7FmcAJVehwp3r16OwV/WIlOyyn19hh33LOQo
5HW1OlGBLn7sqdIuJX8VIOpgN3E4b3zf9vXjZGWMBLUP1AGXT58mwx5U98BDZ4Sd
I/4y3lwuGE+LR4zib2Q9
=sL2d
-----END PGP SIGNATURE-----

--Apple-Mail=_88EB09B3-32A6-46DC-B5E4-2293C48B2C65--

- Raw text -