Mail Archives: geda-user/2015/10/19/17:06:35
> By default, the schematic references the package and stores the picks of
> the author.
My idea allows for "something" to choose the package based on whatever
else the user might have provided. For example, if I specify SOT-23
and my library only has one SOT-23 option, that's enough to specify
the package without having to explicitly specify the package.
That way you can reduce the set of matching parts a little at a time
instead of having to pick a final package up front.
> This sounds a lot like the "package" scenario I described above.
Yup :-)
My way of using it would be to have symbols keep their symbolic pin
"numbers" like A,B,Y or B,C,E. Footprints would have numeric pin
numbers as usual. The "package" would include a mapping from symbolic
to numeric pins for that package. The netlister would apply the
conversion based on which "package" was chosen.
> Except that I deliberately did not imagine a (relational) data base
> but plain files.
Me neither, and since you're quoting what was originally written by
me, let me add this quote from later on in that document:
"How is the database stored? I'm not going to specify that - it's
irrelevent."
- Raw text -