> How do you want to handle multiple vendors with different vendor part > numbers?
Separate tables. In my dream world, symbols have values (like 2.32k) and a footprint class (like "0603"). Footprints can be defaulted (in the export step, not the symbol) so I don't have to fill in "0603" for nearly every discrete. Various tables map symbol names, values, and footprint classes to specific manufacturer parts and footprints/pinouts (like 0603L-dj.fp), and separate tables map manufacturer info to vendor info to optimize purchases. If you put a vendor/vendorpartno in the symbol to "heavify" it, it overrides the default table search. Likewise, you could have a separate table that maps refdes's to vendor numbers. So, a diode.sym with "3A" and "0603" would map to an IR number and 0603dj.fp, mapping "A" and "C" pins to the footprint's pins 1 and 2. Separately, the IR number would map to a digikey number and pricing. Of course, my dream world includes support for slotting via the mapping table rather than in the symbol, and a "table" object in gschem that lets you map refdes+pin to net, for power pins (symbolic pin names, like AVdd, of course - they get mapped to one or more physical pins via the slot map you get when you choose a specific vendor pn/footprint) So, in my dream world, there's exactly one 2-NAND gate symbol, for example. Mapping that to a specific gate in a specific part, with pinning, power, manufacturer and vendor information, pricing, and footprint infomation, is all done by a separate database (in whatever form). _______________________________________________ geda-user mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
