Yep, a lot of our designs here start with this is what it has to do and this is where it has to fit. Physical size limitations are imposed.
On Fri, 2007-12-21 at 10:44 -0600, John Griessen wrote: > Steve Meier wrote: > Project matters of course, and is a good place to define different DRCs. > > > 3) If the project is a circuitboard then before then before the netlist > > can be generated at least the package has to be selected (passive) and > > often the device (active). > > A device complete with package and required values, manufacturor is > > called a "component"? If the project is a circuit either asic or fpga > > then generic types are probably going to be translated into standard > > logic cells? > > I just decided to trash a part I thought was "nifty" for assembly difficulty > reasons. > pcb parts have constraints such as placement courtyard in a 2D sense, > but package height is a big deal too, > and the 3D zone it needs to reserve during assembly > maybe deserves its own data type such as: > > * placement keepout volume > * placement robot keepout > * placement no-fly zone > * placement skyprint > * placement collision volume > * placement canyon > * placement wall > > Wall seems the most compact terminology (in English) to refer to this by. > > John Griessen > > Ecosensory Austin TX > > > _______________________________________________ > geda-user mailing list > geda-user@moria.seul.org > http://www.seul.org/cgi-bin/mailman/listinfo/geda-user _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user