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;
        bh=i49EFWWwz32+SQ4eagMzoZMI2/tGmKJc5UB3AHt0L3k=;
        b=gsebdzcCbf334+PjWn24/UYlhUKr9GRTHuu4kP7rmEeLadgsU+0q6wvXP9waQH4pfa
         uGZR6uLf62en1CsFNv1o56TJqXqYmuP7xlBXqvPPWUaPhX7jrhnTO4vrtiTp9t3DTv/x
         p+6hgnT77SxDsWT6ISNA1Yd4+DctZmVrnqKlQxAvN/kOWw76SrBwlmWJ6knyDTQvEZkK
         aEom1Ur4BoN7sADdKglwga2y2Q3/BJN4FhJFkHEMO93AAcBBh4xPg1KZV0RHG02TNA47
         vOIHXLLbwXaCFVV5rJxitUL/SDFHEIrUWRVUJ0tXDp0cQsuvBeEf/5etQtGcmmiYZEQt
         XPKw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:in-reply-to:references:date
         :message-id:subject:from:to;
        bh=i49EFWWwz32+SQ4eagMzoZMI2/tGmKJc5UB3AHt0L3k=;
        b=ck1q2icKqvFxkajF4kQJ82Vg3+szKL6Gu17AYZfk0omaOSkNTQoe7GfJuc6AkUwOPo
         QT4uXkyyR0JXAC+kZhXk9AVuX+vuiPZoVd+gIc3POYaFOkqXly59upApTAlk1/pGSZ8g
         pqkTB+nBGiDBj5P2YGKQVLTMptkyYOoZzz+e+6pbsD/OSx/dMphiOwtLQjPOQbrmGQd9
         aen+EiKcvWciBANxxEtBPPQKSCK1V05aQlcLleH7XYMA/dhypl/e/s1lfy49UIvldxPF
         EG3EILhJGGnk8hCGLTGMlEHwxsJUsRgdBAfi8btLmiFjxQ1FgkKzTpqWnPWo8hoozEgb
         p7fQ==
X-Gm-Message-State: AD7BkJKUjWLw5r810AzdDSViCAquqi3nFcouT4Umsbb45+77iQ3599ZuvOUFJuFMF28auR2M2SgqzRl6tFMivg==
MIME-Version: 1.0
X-Received: by 10.182.196.37 with SMTP id ij5mr17546725obc.24.1457446575959;
 Tue, 08 Mar 2016 06:16:15 -0800 (PST)
In-Reply-To: <56DECB0E.2070906@m0n5t3r.info>
References: <56DCAE39 DOT 7020204 AT m0n5t3r DOT info>
	<nbijrc$t4t$1 AT ger DOT gmane DOT org>
	<CAHUm0tNohrmDf2oLQAWer_LYSPj9DZzquTdYM-kTgpaM9qO5Lg AT mail DOT gmail DOT com>
	<20160307015049 DOT 097EF8153704 AT turkos DOT aspodata DOT se>
	<CAHUm0tNztZc5nNTtC6in0MdihZnmkX0mG4UBmquSc+cT4nzEeQ AT mail DOT gmail DOT com>
	<20160307123849 DOT AF59B8153706 AT turkos DOT aspodata DOT se>
	<CAHUm0tPMRfV9ub3PXpKAGs9jEWKLJAZxnnwV_OGt38sHkMVv_g AT mail DOT gmail DOT com>
	<nbkgc4$rqd$1 AT ger DOT gmane DOT org>
	<56DECB0E DOT 2070906 AT m0n5t3r DOT info>
Date: Wed, 9 Mar 2016 00:46:15 +1030
Message-ID: <CAHUm0tO3PZD7PyA=VpAWM+kgwc=eNGEsoVptXdopMSuRbJvwwg@mail.gmail.com>
Subject: Re: [geda-user] Valve / nixie symbols
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=089e0149d0747074d6052d8a39a5
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

--089e0149d0747074d6052d8a39a5
Content-Type: text/plain; charset=UTF-8

>
> ... and workflow nightmares :D (no, really, I had to redo a schematic
> because I needed some footprints, found Erich's kicad converted stuff on
> gedasymbols, and then I thought "let's get all of gedasymbols and add it
> to the component library, what could possibly go wrong?")
>
> some curation will be needed somewhere, and things will still need
> manual tweaking to integrate nicely, because conventions may differ: for
> instance, those converted nixie footprints have alphanumeric pin names
> (A, LHDP, RHDP), while the convention I was aware of is pin name == pin
> number (so my symbol's pins didn't match up with footprint pins);
> however, changing the footprint pin names was easy, I very much prefer
> this to drawing the thing from scratch :)
>
> another example of clashing conventions is an Arduino nano symbol (I
> think also from Erich), which has pins very tightly packed and
> everything aligned at 25 grid units, not 100 like regular symbols.
>
>
I have been reluctant to put much more onto gedasymbols just yet because of
the need for curation, and the very arduino symbols you refer to prompted
my enforced pins spacing code which can enforce a specified spacing (when I
nearly lost my mind trying to wire up an arduino nano in gschem with
oddball pin spacing).

In doing this, though, other silk elements that prettify the symbol may be
ruined.

My impression is that the worst offenders are symbols that have been
converted to kicad with an eagle ulp script - they seem to have some very
odd pin naming conventions.

My eagle -> kicad code tries to be more sensible, and applies the
(multiple!) pin mappings provided in the eagle deviceset (symbol flavour ->
particular footprint) to create distinct symbol versions with an associated
footprint also converted from Eagle.

As you say though, the hard work is the geometry, and pin mappings often
need to be verified before sending a board off for production.

I will try to flag oddball spacings and prompt the user to enforce  a
preferred pin spacing.

Thanks for the feedback.

Erich.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><span class=3D""></span><span c=
lass=3D""></span><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<span class=3D"">
</span>... and workflow nightmares :D (no, really, I had to redo a schemati=
c<br>
because I needed some footprints, found Erich&#39;s kicad converted stuff o=
n<br>
gedasymbols, and then I thought &quot;let&#39;s get all of gedasymbols and =
add it<br>
to the component library, what could possibly go wrong?&quot;)<br>
<br>
some curation will be needed somewhere, and things will still need<br>
manual tweaking to integrate nicely, because conventions may differ: for<br=
>
instance, those converted nixie footprints have alphanumeric pin names<br>
(A, LHDP, RHDP), while the convention I was aware of is pin name =3D=3D pin=
<br>
number (so my symbol&#39;s pins didn&#39;t match up with footprint pins);<b=
r>
however, changing the footprint pin names was easy, I very much prefer<br>
this to drawing the thing from scratch :)<br>
<br>
another example of clashing conventions is an Arduino nano symbol (I<br>
think also from Erich), which has pins very tightly packed and<br>
everything aligned at 25 grid units, not 100 like regular symbols.<br>
<br></blockquote><div><br></div><div>I have been reluctant to put much more=
 onto gedasymbols just yet because of the need for curation, and the very a=
rduino symbols you refer to prompted my enforced pins spacing code which ca=
n enforce a specified spacing (when I nearly lost my mind trying to wire up=
 an arduino nano in gschem with oddball pin spacing).<br></div></div><br></=
div><div class=3D"gmail_extra">In doing this, though, other silk elements t=
hat prettify the symbol may be ruined.<br></div><div class=3D"gmail_extra">=
<br></div><div class=3D"gmail_extra">My impression is that the worst offend=
ers are symbols that have been converted to kicad with an eagle ulp script =
- they seem to have some very odd pin naming conventions.<br><br></div><div=
 class=3D"gmail_extra">My eagle -&gt; kicad code tries to be more sensible,=
 and applies the (multiple!) pin mappings provided in the eagle deviceset (=
symbol flavour -&gt; particular footprint) to create distinct symbol versio=
ns with an associated footprint also converted from Eagle.<br><br></div><di=
v class=3D"gmail_extra">As you say though, the hard work is the geometry, a=
nd pin mappings often need to be verified before sending a board off for pr=
oduction.<br><br></div><div class=3D"gmail_extra">I will try to flag oddbal=
l spacings and prompt the user to enforce=C2=A0 a preferred pin spacing.<br=
><br></div><div class=3D"gmail_extra">Thanks for the feedback.<br><br></div=
><div class=3D"gmail_extra">Erich.<br></div></div>

--089e0149d0747074d6052d8a39a5--