Ross Amans Hardware Design Engineer Biometric Access Co 512-426-9252 (cell)
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Doty Sent: Tuesday, June 03, 2008 11:58 AM To: gEDA developer mailing list Subject: Re: gEDA-dev: netlist route styles On Jun 3, 2008, at 10:19 AM, Kai-Martin Knaak wrote: > On Tue, 03 Jun 2008 08:41:09 -0600, John Doty wrote: > >>> stderr / stdout warning that there might be out-dated footprints for >>> certain files. >> >> Unacceptable. In a large project, such warnings are lost in the spew. > > Those, who actually work on large projects will easily adapt and > look for > these warnings, if they prove to contain critical information. grep > and > awk are no rocket science. Not rocket science, but constant vigilance. The result of a "make" should reflect changes you've made: you shouldn't have to do a bunch of extra checking every time. When you're really doing rocket science, you have to minimize these distractions ;-) As much of the unnecessary messages must be removed, so as to optimize your searching for items to fix. An example is when you run valor on a brd file. Many thousands of messages can be generated for a design, but most do not have to be fixed. The urgent and important ones are hidden in the list, and so you have to touch each one to be sure that you did not miss the critical ones. Many hours of wasted work to insure a good product. John has it right. > > >> When I change a symbol to fix a pin assignment, part number, >> footprint, >> underlying hierarchical schematic, etc., I expect that change to >> propagate. > > I don't -- at least not automatically and by default. This kind of > change > all too easily breaks existing schematics or layouts. Because of > this, I > prefer an update of symbols or footprints only if I explicitly choose > so. That's what your project symbol repository is for. When the project is completed, the symbols for that project are in the repository, and won't change unless you want them to. When importing schematics into a new project, you need to import their symbols, too. But then, you can fix the symbols to reflect the requirements of the new project without disturbing the old project. > > > >> With symbol collections customized for the project, it's easy to move >> schematics from project to project (especially if you turn off >> automatic >> promotion of device and footprint attributes). So, low_noise_npn.sym >> represents BCX70K in an SOT23 in one project, 2N930JANTXV in a can in >> another. > > IMHO the risk of unwanted side effects of this approach, will more > than > compensate for the advantage. Such systematic changes should better be > applied by little search-and-replace scripts. Absolutely not! I don't want to replace *every* 0603 with an 0201, only those where, by using a symbol with a project default, I have made the decision that there's no overriding electrical requirement (like power dissipation) that forces a particular package choice. The search-and-replace approach is useful sometimes, but it is generally *more* dangerous. > > ---<(kaimartin)>--- > -- > Kai-Martin Knaak tel: > +49-511-762-2895 > Universität Hannover, Inst. für Quantenoptik fax: > +49-511-762-2211 > Welfengarten 1, 30167 Hannover http://www.iqo.uni- > hannover.de > GPG key: http://pgp.mit.edu:11371/pks/lookup?search=Knaak > +kmk&op=get > > > > _______________________________________________ > geda-dev mailing list > [email protected] > http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ [EMAIL PROTECTED] _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
