Mail Archives: geda-user/2015/12/30/03:23:09
--Apple-Mail=_BADC9CFD-5979-461C-BAEA-BD78C1436539
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252
On Dec 30, 2015, at 12:58 AM, gedau AT igor2 DOT repo DOT hu wrote:
>=20
>=20
> On Wed, 30 Dec 2015, John Doty wrote:
>=20
>>=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?t modify. Indirectly =
through through additional scripts, of course, which is my proposal.
>=20
>=20
> That is not a property of the format we choose. That's a property of =
the program. If we go that way, the only acceptable format would be one =
of the formats osmond can already directly export.
>=20
>=20
>>=20
>> How would you implement this for Osmond PCB?
>=20
> I'll always show both directions.
>=20
> [gschem] --sch--> [gnetlist] --whateverformat1--> [osmond]
> [osmond] --whateverformat2--> [script] --patch--> [gschem]
My proposal was:
[gschem] =97sch =97> [gnetlist] =97osmnet =97> [osmond]
[osmond] =97osmnet =97> [script1] =97canonicalnet =97> [script2] =97patch =
=97> [gschem]
Not much different, except that I=92ve separated osmond-specific script1 =
from general-purpose script2.
>=20
> Depending on the "whateverformat2", the script may need access to the =
original netlist (form the gschem->osmond path).
Generally script2 will, yes.
> Also depending on the format the script may have major functionality =
overlap with gnetlist. If that's the case, it may be reasonable to =
implement the script within gnetlist.
Unlikely.
>=20
> This is one possible flow. There are other possible flows with other =
tools. The one currently implemnted is:
>=20
> [gschem] --sch--> [gsch2pcb] --multiplefiles--> [pcb]
> [pcb] --patch--> [gschem]
>=20
> My point was that the fact osmond can't directly emit the patch format =
doesn't invalidate other flows where it is possible.
I never said it did, but a general purpose toolkit should implement =
general mechanisms. That doesn=92t invalidate shortcuts for special =
cases.
> It also doesn't tell anything about the format itself - it only tells =
anything about osmond. It also doesn't seem to be more complicated than =
the other direction (actually looks exactly the same in complexity).
>=20
> Thus I can't agree with saying that either the flow or the format is =
not generic enough because you need the same extra step in =
osmond->gschem direction that you need in gschem->osmond direction.
Generally you need to work through netlist and BOM in both directions.
>=20
>=20
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
--Apple-Mail=_BADC9CFD-5979-461C-BAEA-BD78C1436539
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
iQIcBAEBCgAGBQJWg5RXAAoJEF1Aj/0UKykRj/0P/ixufBIX0CiKuPHjz5zXfSI4
ad94W67L2rbQcv4aFb8zumXxiT/VVjp6IBiT4Ezr/Cmx5TEqMpnxUsjs3DIzzh/V
NP4ssWi64fjsTYNHBl1A5lDhcSQ4kF4XWcfiWYxmAfQ+3Qgp62y2n/LYxlVz2oJy
XKu3vx/n5HUL6aXx7s/nLhxMhnxpCqCfsz8GyAM36wbdOAzWCjigqwtS2tfGSEfG
3WMKATjzC/0LTY8D0GaARru8wXgKZFsUNZzPvszgyZDNMdFp+Xu1n5Dx3JjfdrE/
CPiBPVjDJ0N5UJYmWqAtBv0pxMASeLSU/QQb1y6BJlXQnI3nkpUoGxAU7CD1rt0y
fLNkoRf3y1CskqJJjUBv/vV+T1BzZeA3+fn8hoHwRpiuEhO4eviI2AVKlwaKY7gY
n+CO8HEwc53hRffNqbk7QBMd6fNw9Du3rEI5Ps+G5xhLzeSikC1gUhBZWXc9WbYC
pDto04TznrnISbzWmd1NiCpTG1AnJexlgo6u1PbaTCiPiNB2cnbxDs8aH57qgDO+
dTyuv2JwxTlnbbyCMVkw/BGlC8gHoum0vxsSi8H0xDbtg/gmaggNRb9kIso7P0Lx
CNbYCWjaLH+jT8hlbike85UcDxmCsQKtHckW+gpjPPDRRQ/c8Fto6SKvZdkJNfFE
qEDpkwx5A7k7GHjWKhH/
=jyE5
-----END PGP SIGNATURE-----
--Apple-Mail=_BADC9CFD-5979-461C-BAEA-BD78C1436539--
- Raw text -