X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Thu, 31 Jan 2013 04:26:54 +0100 (CET) X-X-Sender: igor2 AT igor2priv To: geda-user AT delorie DOT com X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu" From: gedau AT igor2 DOT repo DOT hu Subject: Re: [geda-user] [patch] Pinnumbers in mosfet-with-diode-1.sym In-Reply-To: <1359555319.2295.9.camel@AMD64X2> Message-ID: References: <20130130090351 DOT GE32216 AT fi DOT muni DOT cz> <1359555319 DOT 2295 DOT 9 DOT camel AT AMD64X2> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 On Wed, 30 Jan 2013, Stefan Salewski wrote: > This is something what confused me too when I used gEDA/PCB for the > first time, but there exist no easy solution. You should find > discussions of this problem in in the wike and in this mailing list, or > maybe on in older initial gEDA mailing list. DJ and others have mode > suggestions to solve such kind of problems, some suggestions use a > database to solve it. 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.