[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: gEDA-user: Solving the light/heavy symbol problem

> Hierarchy isn't the only reuse scenario. Consider transition from
> breadboard to prototype to production. A top-level schematic might
> not change, even though attributes of parts might change (different
> packages, tighter specs, ...). In that case, the instance-specific
> data can't be in *any* schematic.

Up to now, we've been using the schematic as the "master" files for
the design.  Perhaps this is a bad idiom?  Perhaps "the design" should
be some other data, which uses the schematic as but one of its inputs?

geda-user mailing list