X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=rcH++7BUjdDFkMbLLRPh+T2BDcCuj6lyaS9r3NyEd4I=;
        b=l4g3LwK+uw/9WR/UYSoXdUFS85dtSGg1i6RVbNA6W+0VzYowK0iHpvg36S6lMOl6UD
         1NqryBQWzZkJD5bODAsrAT1ZxEypF0b2lDw3+8YhE8acQDYJ6wsFI3GU10Kbwx00vnlG
         P67IZLuNxn4OsWo1J2mrREYdeXu/9RvRwcsZpe8NygWrkgd/KIqthhxO/7h1KVptpee9
         yOkGOaUXyi/I5OEgxGKFlcBcJ9f8Ei70C8960LuwWR/uCEddR8G762eODYt3rTilaFKg
         TBUlQYo4qX2jI9ZVaSVBk8a29v1A0BrDw1i/znHaiZyLFjkbImNS5dmKrGq8HqCm19Nt
         ceUA==
MIME-Version: 1.0
X-Received: by 10.202.79.137 with SMTP id d131mr16504949oib.37.1450914488198;
 Wed, 23 Dec 2015 15:48:08 -0800 (PST)
In-Reply-To: <CAJXU7q-tRF5mWBaT+4qA9Ct8YaLZsFQ1E-wcs6ZKx3+5tkaqDQ@mail.gmail.com>
References: <CAJXU7q9ToaWE+wVJcF76yqHhjYZc5j95VL64cXPey-x4s_j9OA AT mail DOT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1512221634081 DOT 9035 AT igor2priv>
	<CAJXU7q_oFvUsdQ4zB+9Kp31dhOQPZa7b21AMZ9g_=VpYN1gAnw AT mail DOT gmail DOT com>
	<B7FF4997-34E5-4E61-AD74-28BE54E45801 AT noqsi DOT com>
	<CAJXU7q9SO+beJYXCdP4iubBnXu7WP1TrqcbJwvRtYz-2YgFQvw AT mail DOT gmail DOT com>
	<n5dgdv$g5t$1 AT ger DOT gmane DOT org>
	<CAHUm0tPZD-BLh1C4oYbYyE7cz-3JGjTk1SVtacugRYtcQm1k0w AT mail DOT gmail DOT com>
	<CAJXU7q-tRF5mWBaT+4qA9Ct8YaLZsFQ1E-wcs6ZKx3+5tkaqDQ AT mail DOT gmail DOT com>
Date: Thu, 24 Dec 2015 10:18:08 +1030
Message-ID: <CAHUm0tNf+tL2PjSYK+uJSqpWTmdprhzf+5LGxGHQF5m29fMiJA@mail.gmail.com>
Subject: Re: [geda-user] Cross project collaboration on data models
From: "Erich Heinzle (a1039181 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user <geda-user AT delorie DOT com>
Content-Type: multipart/alternative; boundary=001a113d83bcab2c680527995a4a
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

--001a113d83bcab2c680527995a4a
Content-Type: text/plain; charset=UTF-8

Re: s-expression changes to kicad schematics files

thanks for the heads up. The footprint conversion utility has legacy and
s-file parsing; supporting both wasn't too hard - they just nested things
in a bunch of parantheses.

I have just tweaked the footprint conversion utility to behave properly
with kicad modules generated by the madparts python tool. The next step
will be implemenin export from the madparts footprint creation utility
directly.

The madparts developer http://madparts.org  seems to have gone a long way
towards the unified approach being pondered in this thread.

Cheers,

Erich

--001a113d83bcab2c680527995a4a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Re: s-expression changes to kicad schematic=
s files<br><br></div>thanks for the heads up. The footprint conversion util=
ity has legacy and s-file parsing; supporting both wasn&#39;t too hard - th=
ey just nested things in a bunch of parantheses.<br><br></div><div>I have j=
ust tweaked the footprint conversion utility to behave properly with kicad =
modules generated by the madparts python tool. The next step will be implem=
enin export from the madparts footprint creation utility directly.<br></div=
><div><br></div><div>The madparts developer <a href=3D"http://madparts.org"=
>http://madparts.org</a>=C2=A0 seems to have gone a long way towards the un=
ified approach being pondered in this thread.<br></div><div><br></div>Cheer=
s,<br><br></div>Erich<br></div>

--001a113d83bcab2c680527995a4a--