Re: gEDA-dev: collecting/sharing scripts

[Dan McMahill <dan-at-NOSPAMmcmahill_dot_net>]

Igor2 wrote:
> Hi!
> 
> Yesterday I wrote a little script that helps me matching the pinout of
> stock gschem symbols with the PCB footprints. In gschem I add a comment
> property to any of the symbols in form "pinout A=1 B=3 C=2". After
> running gsch2pcb I run this script on the project file and it fixes up the
> netlist file using the alternate pinouts in comments.
> 
> I am not sure this is the proper solution, but it's easier than creating a
> new symbol every time I have the same symbol for a different package.

I think that this is an issue which really should be addressed.  In at 
least some CAD systems (Accel/PCAD is what I have in mind here), a 
component consists of a symbol, a footprint, and a small spreadsheet 
type database that says:

symbol pin #1 is "IN+" and is footprint pin "3"
symbol pin #2 is "IN-" and is footprint pin "2"
etc.

Thats also where slotting information goes.

I wonder if maybe the way to go is to start with a basic symbol where 
you've put things like

@footprint@
@pin1@
@pin2@

and a few other entries in the symbol as place holders and then have a 
script that runs perhaps at library build time and whenever the usr 
wants to run it that builds up heavy symbols from the generic symbols.

For those who don't like "heavy" symbols, I'll note that to some extent 
we don't really have "light" symbols but rather "medium" and "heavy" 
symbols.  Because as Igor is seeing, the true pinout is part of the symbol.

-Dan


_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev