Ales Hvezda wrote: > gschem should do the mapping? Hmmm. I'll have to consider that. > Is that what people really want? > > Option A. Inside of gschem > > Plop down a light component. Open up some sort of dialog which > allows you do specify the footprint and the appropriate logical to > physical mapping is applied. Save schematic, run gnetlist, and then > layout.
Yes, maybe, or in gattrib as well. I like the concept of annotations going in both directions, pcb to gnetlist to gschem and the other direction. A dialog, could be one optional way to get the mapping of footprints done, and scripts could be the other. Having all the details of pin numbers, names and sequences be attributes that can be edited, and changed by scripts is good even though it makes it possible to UNDO the "fab checked for accuracy" attribute of a footprint. I can imagine using a gattrib style editor that also lets you check for consistency of data -- if you edit pinseq and it's in a defined "vetted" footprint you get a reminder that you are over-ruling that status of being checked. Being able to group attributes that go together is one way to implement importing a heavy symbol definition with footprints into gattrib or gschem. To me, an attribute group is another name for a heavy symbol, where some of the grouped attributes are the symbol graphic parts and locations of attribute text and visibilities. John Griessen _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
