Re: gEDA-user: Parts DB API

[John Doty <jpd@xxxxxxxxxxxxx>]

On Dec 18, 2007, at 2:32 PM, Peter TB Brett wrote:

> "Rewrite the component library C & Scheme APIs, and make a new GUI  
> for it in
> gschem" is achievable (just).  Ideally, I'd like to be able to do  
> it in a
> tidy, self-contained way.

May I suggest the following path to the future? I believe it's pretty  
simple.

Define a new attribute, "part=". Have it refer to an entry in a file,  
"parts". Now, for example, I might attach the attribute "part=BCX70K"  
to a light NPN transistor symbol. In the file "parts", I might place  
the following:

BCX70K
	device=2N930JANTXV
	footprint=TO206AA
	pinnumber=1:C
	pinnumber=2:B
	pinnumber=3:E

The "1:" etc. refer to pinseq, similar to slotting. There may be a  
better way to do this.

Note that I used a part number of a transistor similar to what I  
wanted as the part ID here, but the real part turned out to be  
2N930JANTXV. I could also have used low_noise_npn.

Rules:

Attributes in the parts file override attributes in the symbol and  
schematic.

There is no graphical information in the parts file. For an attribute  
to be visible in the schematic, a visible default/placeholder  
attribute should be visibly present in the symbol or visibly attached  
in the schematic. The attribute value in the parts file then  
overrides the value in the graphics, but the graphical properties of  
the attribute still originate in the graphics.

The "ep" command should rescan symbols and the parts file, updating  
attributes.

Overridden attributes should be greyed out in the attribute editing  
dialog.

I think this requires very few changes and can be generalized in the  
future.

John Doty              Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd@xxxxxxxxx




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