Mail Archives: geda-user/2016/01/09/00:16:02
--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"><<a href=3D"mailto:ged=
a-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>></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>
"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>]" <<a href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delo=
rie.com</a>> wrote:<br>
<br>
> In preferences-->Layers-->Groups some of the layers are listed b=
ut<br>
> 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'd add user defined layers as well. I'd add some logic like &=
quot;XOR this<br>
layer with that, and use it as conductive 2."<br>
<span class=3D""><br>
> For padtack which could be used for: pins, pads, via ordinary, via<br>
> buried, via blind: I suggested a group of ordinary drawing primitives<=
br>
> could be grouped together but no one said if this is a bad or good<br>
> idea. I also suggested this group you call a padstack could be placed<=
br>
> in a library with sub folders for different package types so they<br>
> could be used many times. This might be very far out but a discussion<=
br>
> 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'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'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.=
=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'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--
- Raw text -