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=CE/mlA6zRPPqDSpLFeA3VMiZGfejCGRefvCfZVvD0XU=;
	b=VDO76znRWW2/9EJjg+VnG9a0eqkasRbvBTT7x/tFAM+KgsT6m1DBbJTt/iKM2KxAZM
	vRXXfM7vRbKCZVImMiTwTMh99iMLxb7RXIlYuDtm15F8IOtHtw6N9+xpDqkQ22QdKiff
	ymDHtqpRXy6y/HLhn1Qt9KaG+59A3HN3NdEHPpvkLuGhndSAtUGc0avs3VgD94uw7yCS
	gCqrrMcWxyk+lNgzZtiOH9ec72OuHw18oax2cOLU43xIHAKH67bQIevyKTRaxbQ3wGy8
	wPyGXab5GoPwzcMTRYQzldpDqREwkizmZE7za2j0BLCUDhJNyZeLFroDiVwmDCYFDd38
	qtIQ==
MIME-Version:	1.0
X-Received:	by 10.60.134.78 with SMTP id pi14mr25979409oeb.65.1440486926675;
	Tue, 25 Aug 2015 00:15:26 -0700 (PDT)
In-Reply-To:	<55DBA2B7.1080501@ecosensory.com>
References:	<20150824223846 DOT 0ba61ba7 AT jive DOT levalinux DOT org>
	<55DBA2B7 DOT 1080501 AT ecosensory DOT com>
Date:	Tue, 25 Aug 2015 16:45:26 +0930
Message-ID:	<CAHUm0tNAY8TY485-imFoTHJqRha=99bmO_3a9f_jjpWCU4x8Zg@mail.gmail.com>
Subject:	Re: [geda-user] pcb file format
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>
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

--047d7b47200e917445051e1d7f0a
Content-Type: text/plain; charset=UTF-8

The new kicad s-file format is basically a tree structure using parantheses
to demarcate the nodes. It is easily parsed by simple utilities, and is
quite human readable.

We could do worse than to duplicate their format. We also seamlessly get
the benefit of kicad footprint creation tools and footprint libraries.

Perhaps we should list the things a new file format should ideally
support... it seems pointless to implement a new format unless it
significantly extends the usefulness of PCB.... these are in no particular
order, but are features that are hard to do with the current format.... a
few things that come to mind include:

text in footprints (kicad supports hidden and visible flags) +/- font
selection
vias between layers
bezier curves (these are already supported by gschem's symbol format)
obround pad/pin definitions
a standard range of default layers - again, we could do worse than to copy
kicad's 32 layer structure.
slots, non plated and plated
perhaps a rotation value for an element in a layout

Just some thoughts.

Erich.



On Tue, Aug 25, 2015 at 8:33 AM, John Griessen <john AT ecosensory DOT com> wrote:

> On 08/24/2015 03:38 PM, Lev (leventelist AT gmail DOT com) [via
> geda-user AT delorie DOT com] wrote:
>
>> Here I propose the file format of the next generation of PCB. The file is
>> an
>> sqlite database.
>>
>
> I like it.  And go ahead and use Fossil, the DVCS by the same authors as
> sqlite
> for the project.
>
> "and you can now start throwing eggs,
> potatoes, tomatoes."
>
> Oh, maybe it is not super compact.  How different in file size is it?
> sqlite probably has easy to use compression for the file based DB...
>
> John, not throwing anything
>

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

<div dir=3D"ltr"><div><div><div><div><div><div><div><div>The new kicad s-fi=
le format is basically a tree structure using parantheses to demarcate the =
nodes. It is easily parsed by simple utilities, and is quite human readable=
.<br><br></div>We could do worse than to duplicate their format. We also se=
amlessly get the benefit of kicad footprint creation tools and footprint li=
braries.<br><br></div>Perhaps we should list the things a new file format s=
hould ideally support... it seems pointless to implement a new format=20
unless it significantly extends the usefulness of PCB.... these are in no p=
articular order, but are features that are hard to do=20
with the current format.... a few things that come to mind include:<br><br>=
</div>text in footprints (kicad supports hidden and visible flags) +/- font=
 selection<br></div>vias between layers<br></div>bezier curves (these are a=
lready supported by gschem&#39;s symbol format)<br></div>obround pad/pin de=
finitions<br></div>a standard range of default layers - again, we could do =
worse than to copy kicad&#39;s 32 layer structure.<br></div>slots, non plat=
ed and plated<br><div>perhaps a rotation value for an element in a layout<b=
r></div><div><br></div><div>Just some thoughts.<br><br></div><div>Erich. <b=
r></div><div><div><div><br><div><br></div></div></div></div></div><div clas=
s=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Aug 25, 2015 at 8:=
33 AM, John Griessen <span dir=3D"ltr">&lt;<a href=3D"mailto:john AT ecosensor=
y.com" target=3D"_blank">john AT ecosensory DOT com</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"><span class=3D"">On 08/24/2015 03:38 PM, Lev (<a =
href=3D"mailto:leventelist AT gmail DOT com" target=3D"_blank">leventelist AT gmail DOT c=
om</a>) [via <a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">ged=
a-user AT delorie DOT com</a>] wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Here I propose the file format of the next generation of PCB. The file is a=
n<br>
sqlite database.<br>
</blockquote>
<br></span>
I like it.=C2=A0 And go ahead and use Fossil, the DVCS by the same authors =
as sqlite<br>
for the project.<span class=3D""><br>
<br>
&quot;and you can now start throwing eggs,<br>
potatoes, tomatoes.&quot;<br>
<br></span>
Oh, maybe it is not super compact.=C2=A0 How different in file size is it?<=
br>
sqlite probably has easy to use compression for the file based DB...<br>
<br>
John, not throwing anything<br>
</blockquote></div><br></div>

--047d7b47200e917445051e1d7f0a--

- Raw text -