gEDA-dev: My multiple footprint plan

[Cory R. Cross]

Hi all,

I'm working to integrate gEDA into an inventory/parts database. My first,
easy step will be to write a small program that will load an existing
symbol, like 7400-1.sym, and add an attribute called 'mapping=', which
would link to a file containing (original_pin_number,final_pcb_pin_number)
tuples and a package identifier, then insert into a running instance of
gschem. If this proves too difficult, I can always add in the attribute
manually.

The second half of this would be hacking gnetlist/gsch2pcb to change the
output pin numbers when they generate the netlist and pick a different
footprint to add into the board file, if the mapping= attribute exists and
points to a valid file.

I anticipate this taking a few hours at most. Anything major I'm missing?

Thanks,
Cory Cross

ps I'll soon have a lot of symbols and footprints to upload.

pps
Eventually, I want implement a graphical viewer that shows the physical
components that have been chosen so far and allow you to map the open
slots/sections to particular symbols. For example, some Atmel AVRs have an
analog comparator builtin and it would nice to put a generic part for that
initially, then later be able to tie it to a distinct comparator or put it
in the micro. Yes, I am mainly influenced by some of your past writings.