X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:x-received:in-reply-to:references:date:message-id
         :subject:from:to:content-type;
        bh=CxQGQzqXlx+PobLbszHpSmDBiFqKbHeXmykgmR7oWiM=;
        b=oD5zLFaBTZpBWJJGLMlTkFq080u454bPV6MOmbPGH+CFwhJqNHiYaeYAfdm8QSxaxF
         L6Ii1F3Us5l6P0qfQ+u5/ndRrMRPiacGMOwfpFvr6Z46JKYDwQQbBLMV0xGIVJruUlO9
         3XEB9c+OCC52vQwpDc1FC0gR66fnZxjHZ4f9YOxqm4YidosbcSe/Vquff+en9r5Bpqxq
         BTngC7cygYHizL4r6PZilX2FwAf9TkNe4ij6lutiTyX3VSL1o/1SL/B6gu3GPpo2T6Dd
         Ty42UNQgEj29TgAJlIYBWMAxac8CefI/CA4X3l6K68ZUTAQVwV55F7eOetePf0vo28OT
         HraQ==
MIME-Version: 1.0
X-Received: by 10.60.14.193 with SMTP id r1mr6238320oec.27.1359623976255; Thu,
 31 Jan 2013 01:19:36 -0800 (PST)
In-Reply-To: <alpine.DEB.2.00.1301310418000.7105@igor2priv>
References: <20130130090351 DOT GE32216 AT fi DOT muni DOT cz>
	<1359555319 DOT 2295 DOT 9 DOT camel AT AMD64X2>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1301310418000 DOT 7105 AT igor2priv>
Date: Thu, 31 Jan 2013 10:19:36 +0100
Message-ID: <CACwWb3Atq-VVqXsjgfzRU0aibpcGeHWmcFzmzMEX2NMawT+ECw@mail.gmail.com>
Subject: Re: [geda-user] [patch] Pinnumbers in mosfet-with-diode-1.sym
From: Levente <leventelist AT gmail DOT com>
To: geda-user AT delorie DOT com
Content-Type: multipart/alternative; boundary=e89a8ff252ee21ffd204d4922078
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

--e89a8ff252ee21ffd204d4922078
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jan 31, 2013 at 4:26 AM, <gedau AT igor2 DOT repo DOT hu> wrote:

>
> The solution I found easy is my devmap script: I can use the generic
> symbols with letters, then I attach a devmap attribute telling which
> actual device and footprint shall be used (e.g. bc817_sot23) and the rest
> is done while converting from gschem to pcb. Actual device maps are plain
> text files that describe attributes to be added/overwritten with a pinmap
> functionality that can replace pin numbers by value (so that pin C becomes
> pin 3). Device maps are easy to write, easy to maintain and VCS friendly.
> Schematics with the above "bc817_sot23" next to the symbol are readable,
> still not overtaxed with extra text.
>
>
+1

I do the same.

Levente

--e89a8ff252ee21ffd204d4922078
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Thu, Jan 31, 2013 at 4:26 AM,  <span dir=3D"l=
tr">&lt;<a href=3D"mailto:gedau AT igor2 DOT repo DOT hu" target=3D"_blank">gedau AT igor=
2.repo.hu</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im"><br>
The solution I found easy is my devmap script: I can use the generic symbol=
s with letters, then I attach a devmap attribute telling which<br></div>
actual device and footprint shall be used (e.g. bc817_sot23) and the rest i=
s done while converting from gschem to pcb. Actual device maps are plain te=
xt files that describe attributes to be added/overwritten with a pinmap fun=
ctionality that can replace pin numbers by value (so that pin C becomes pin=
 3). Device maps are easy to write, easy to maintain and VCS friendly. Sche=
matics with the above &quot;bc817_sot23&quot; next to the symbol are readab=
le, still not overtaxed with extra text.<br>

<br></blockquote><div>=A0</div></div>+1<br><br>I do the same.<br><br>Levent=
e<br>

--e89a8ff252ee21ffd204d4922078--