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=aggR9RJmZ5b4Jlzf1yYGM9PUaAG0L6sA0UZfle6139A=;
        b=S/8jmqubKXOw2CQc6Aegr1yZw8zTR1imUYvSTcxSk7cod+9Sojn6xoPlkVYx/o970N
         6MrMvF9RrxA4ojWFfJCvS4Mglu/1zYeVnh4zHcY4ooiOdFjQNjWAgqQxABMDMqRPcQsF
         BrI02zGr/jKr8v8YqbTMwbhqlyS2s4hxurRwzsfSporNetBp1in4uwUbj4njMgYE6WoT
         lbzIIys8iPWL2PsiUh+WBeitfxwr7lJKx0LMaOff1wuYhi2F+aJmEck7/b4GQQ5oS7mr
         ebs1nQ/BemHw7TY645iYCRvE1Igf7flJYL1tWNgVLbgHb2PZ73tnlbjMTBaVLJuMpYgU
         PAzg==
MIME-Version: 1.0
X-Received: by 10.28.23.73 with SMTP id 70mr2242745wmx.37.1452316524410; Fri,
 08 Jan 2016 21:15:24 -0800 (PST)
In-Reply-To: <20160109020345.1e07cb84@jive>
References: <1512221837 DOT AA25291 AT ivan DOT Harhan DOT ORG>
	<D9825C8C-B6FD-4C7F-A8D5-B8AF06253B72 AT noqsi DOT com>
	<CAC4O8c_R5xWLmzj_cz0g0mPWNs6mR4efjXKGBoup8YO6nwnPTA AT mail DOT gmail DOT com>
	<20160106091006 DOT 5F67B809D7A1 AT turkos DOT aspodata DOT se>
	<CACwWb3CcsYJ9KgDFAa5pZqDzfTewhvbuatbxoKUp6PtHRCoa+w AT mail DOT gmail DOT com>
	<20160106133049 DOT 5A0E9809D79B AT turkos DOT aspodata DOT se>
	<CACwWb3Cyk4yLwt3=V1Mu5C4RieOQEjYH3ej5MXZSNnLPbshqDg AT mail DOT gmail DOT com>
	<20160106143629 DOT 4D39D809D79B AT turkos DOT aspodata DOT se>
	<CACwWb3BXbnQXs+DwVVzmC8DrhwOYxPgVyUhZTPL9bM9cJbHimw AT mail DOT gmail DOT com>
	<20160106164022 DOT D0D4E809D79B AT turkos DOT aspodata DOT se>
	<20160106180912 DOT 42ddf4079d91384f206b7c35 AT gmail DOT com>
	<20160106191433 DOT 5dc5cb59 AT jive DOT levalinux DOT org>
	<20160106202817 DOT 56197b2c539d426a1b724c9e AT gmail DOT com>
	<568E09ED DOT 1080508 AT m0n5t3r DOT info>
	<CACwWb3AhSh-+NNu--bVMGZBfjaoA+hHg7gbXnoyNv3oMq=e17g AT mail DOT gmail DOT com>
	<568E6354 DOT 80302 AT m0n5t3r DOT info>
	<20160108002640 DOT 03233b24 AT jive DOT levalinux DOT org>
	<20160108175259 DOT 127a3f073616758434f7edff AT gmail DOT com>
	<20160109020345 DOT 1e07cb84 AT jive>
Date: Fri, 8 Jan 2016 20:15:24 -0900
Message-ID: <CAC4O8c-nqs2+9rgsD-Gsks-wSmJ1eCkJ9PFMi3XqMrYE2FO3Ew@mail.gmail.com>
Subject: Re: [geda-user] (features: layers stack, padstack/vias)
From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Content-Type: multipart/alternative; boundary=001a1145a83a89fcdc0528dfca66
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

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

On Fri, Jan 8, 2016 at 4:03 PM, Lev (leventelist AT gmail DOT com) [via
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:

> On Fri, 8 Jan 2016 17:52:59 +0100
> "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via
> geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> wrote:
>
> > In preferences-->Layers-->Groups some of the layers are listed but
> > not all are listed. What do you think is missing?
>
> I would add explicitly the insulation layers, and documentation layers,
> silks,
> etc. I'd add user defined layers as well. I'd add some logic like "XOR this
> layer with that, and use it as conductive 2."
>
> > For padtack which could be used for: pins, pads, via ordinary, via
> > buried, via blind: I suggested a group of ordinary drawing primitives
> > could be grouped together but no one said if this is a bad or good
> > idea. I also suggested this group you call a padstack could be placed
> > in a library with sub folders for different package types so they
> > could be used many times. This might be very far out but a discussion
> > how it should be done is always a start.
>
> Yes. That would be nice. A library is also a hierarchical structure. It
> contains the pads, padstacks, footprints. Yes, the padstacks are built up
> from primitives.
>
> If I go on, and implement the SQL based file format, it is easy. I defined
> pad
> and padstack tables.
>
> If we go the YAML way, I don't know how to represent that data.
>

The way to think about YAML/JSON is as portable text-based serialization
formats for the couple most popular datatypes that get built into modern
languages, in particular arrays, hashes, and scalar values (basically
numbers and strings).  JSON doesn't support native (non-tree) references so
you have to add your own id field if what you want to refer to doesn't have
already have a unique name.  YAML does.  JSON is much more common but
unfortunately also more noisy.  Some people like the noise because they
don't trust any whitespace-based approach (bad experiences with make).

Britton

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, Jan 8, 2016 at 4:03 PM, Lev (<a href=3D"mailto:leventelist AT gmai=
l.com">leventelist AT gmail DOT com</a>) [via <a href=3D"mailto:geda-user AT delorie.=
com">geda-user AT delorie DOT com</a>] <span dir=3D"ltr">&lt;<a href=3D"mailto:ged=
a-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">On Fri, 8 Jan 2016 17:52:59 +0100<=
br>
&quot;Nicklas Karlsson (<a href=3D"mailto:nicklas DOT karlsson17 AT gmail DOT com">nic=
klas DOT karlsson17 AT gmail DOT com</a>) [via<br>
<span class=3D""><a href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie=
.com</a>]&quot; &lt;<a href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delo=
rie.com</a>&gt; wrote:<br>
<br>
&gt; In preferences--&gt;Layers--&gt;Groups some of the layers are listed b=
ut<br>
&gt; not all are listed. What do you think is missing?<br>
<br>
</span>I would add explicitly the insulation layers, and documentation laye=
rs, silks,<br>
etc. I&#39;d add user defined layers as well. I&#39;d add some logic like &=
quot;XOR this<br>
layer with that, and use it as conductive 2.&quot;<br>
<span class=3D""><br>
&gt; For padtack which could be used for: pins, pads, via ordinary, via<br>
&gt; buried, via blind: I suggested a group of ordinary drawing primitives<=
br>
&gt; could be grouped together but no one said if this is a bad or good<br>
&gt; idea. I also suggested this group you call a padstack could be placed<=
br>
&gt; in a library with sub folders for different package types so they<br>
&gt; could be used many times. This might be very far out but a discussion<=
br>
&gt; how it should be done is always a start.<br>
<br>
</span>Yes. That would be nice. A library is also a hierarchical structure.=
 It<br>
contains the pads, padstacks, footprints. Yes, the padstacks are built up<b=
r>
from primitives.<br>
<br>
If I go on, and implement the SQL based file format, it is easy. I defined =
pad<br>
and padstack tables.<br>
<br>
If we go the YAML way, I don&#39;t know how to represent that data.<br></bl=
ockquote><div><br></div><div style=3D"">The way to think about YAML/JSON is=
 as portable text-based serialization formats for the couple most popular d=
atatypes that get built into modern languages, in particular arrays, hashes=
, and scalar values (basically numbers and strings).=C2=A0 JSON doesn&#39;t=
 support native (non-tree) references so you have to add your own id field =
if what you want to refer to doesn&#39;t have already have a unique name.=
=C2=A0 YAML does.=C2=A0 JSON is much more common but unfortunately also mor=
e noisy.=C2=A0 Some people like the noise because they don&#39;t trust any =
whitespace-based approach (bad experiences with make).</div><div style=3D""=
><br></div><div style=3D"">Britton</div><div><br></div></div><br></div></di=
v>

--001a1145a83a89fcdc0528dfca66--