<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/'><id>tag:blogger.com,1999:blog-31006871.post7924235526110753457..comments</id><updated>2009-01-02T17:29:01.277+02:00</updated><title type='text'>Comments on The Art of Engineering: Light and heavy symbols</title><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://blog.engineersimplicity.com/feeds/7924235526110753457/comments/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/31006871/7924235526110753457/comments/default'/><link rel='alternate' type='text/html' href='http://blog.engineersimplicity.com/2008/10/light-and-heavy-components.html'/><author><name>Duncan Drennan</name><uri>http://www.blogger.com/profile/18356141566912975917</uri><email>noreply@blogger.com</email></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>4</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-31006871.post-2039118517403119971</id><published>2008-11-12T10:56:00.000+02:00</published><updated>2008-11-12T10:56:00.000+02:00</updated><title type='text'>I agree that symbols should be light. Attributes f...</title><content type='html'>I agree that symbols should be light. Attributes for each component should be stored in a database, along with a reference to a symbol. If you draw a schematic for a PCB design you should preferably not place symbols (really!) but a component from the database. The correct symbol with attributes would then be in the design with just one action.&lt;BR/&gt;&lt;BR/&gt;From my experience with Mentor-DxDatabook and Cadence-Capture-CIS as both designer and component-library/database maintainer I believe this is the way to go for any design team that involves more than one person or more than one design. The advantages are numerous.&lt;BR/&gt;&lt;BR/&gt;For gEDA both gschem and gattrib should be database aware for this to work properly. This is an absolute requirement for any schematic capture program to function in a company that does multiple designs.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/31006871/7924235526110753457/comments/default/2039118517403119971'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/31006871/7924235526110753457/comments/default/2039118517403119971'/><link rel='alternate' type='text/html' href='http://blog.engineersimplicity.com/2008/10/light-and-heavy-components.html?showComment=1226480160000#c2039118517403119971' title=''/><author><name>Ronald</name><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://blog.engineersimplicity.com/2008/10/light-and-heavy-components.html' ref='tag:blogger.com,1999:blog-31006871.post-7924235526110753457' source='http://www.blogger.com/feeds/31006871/posts/default/7924235526110753457' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-31006871.post-7535938896828981069</id><published>2008-10-21T13:07:00.000+02:00</published><updated>2008-10-21T13:07:00.000+02:00</updated><title type='text'>A ha! Good point Duncan, one I had not thought of....</title><content type='html'>A ha! Good point Duncan, one I had not thought of. So if you have people who are meticulous when they link up the part name (I'm assuming one specific enough to give all the pinout information and such), then you'll be in good shape. Excellent point!&lt;BR/&gt;&lt;BR/&gt;~Chris</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/31006871/7924235526110753457/comments/default/7535938896828981069'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/31006871/7924235526110753457/comments/default/7535938896828981069'/><link rel='alternate' type='text/html' href='http://blog.engineersimplicity.com/2008/10/light-and-heavy-components.html?showComment=1224587220000#c7535938896828981069' title=''/><author><name>Chris Gammell</name><uri>http://chrisgammell.com</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://blog.engineersimplicity.com/2008/10/light-and-heavy-components.html' ref='tag:blogger.com,1999:blog-31006871.post-7924235526110753457' source='http://www.blogger.com/feeds/31006871/posts/default/7924235526110753457' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-31006871.post-1512529127679137854</id><published>2008-10-20T14:08:00.000+02:00</published><updated>2008-10-20T14:08:00.000+02:00</updated><title type='text'>Hi Chris,All the necessary information is still st...</title><content type='html'>Hi Chris,&lt;BR/&gt;&lt;BR/&gt;All the necessary information is still stored in your schematic, just not in your library. The schematic has detailed part info and so on, but the library does not (attributes are added to the schematic after placing the symbol from the library).&lt;BR/&gt;&lt;BR/&gt;The symbol library just has an opamp symbol (with the correct pin-out), then the part number (and any other attributes) are added to the schematic. The schematic persists over time, and the new engineer should still know what is going on.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/31006871/7924235526110753457/comments/default/1512529127679137854'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/31006871/7924235526110753457/comments/default/1512529127679137854'/><link rel='alternate' type='text/html' href='http://blog.engineersimplicity.com/2008/10/light-and-heavy-components.html?showComment=1224504480000#c1512529127679137854' title=''/><author><name>Duncan Drennan</name><uri>http://www.blogger.com/profile/18356141566912975917</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='04600832983671621308'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://blog.engineersimplicity.com/2008/10/light-and-heavy-components.html' ref='tag:blogger.com,1999:blog-31006871.post-7924235526110753457' source='http://www.blogger.com/feeds/31006871/posts/default/7924235526110753457' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-31006871.post-3582210870762771302</id><published>2008-10-20T13:58:00.000+02:00</published><updated>2008-10-20T13:58:00.000+02:00</updated><title type='text'>Hi Duncan,Even though I understand the rigors of m...</title><content type='html'>Hi Duncan,&lt;BR/&gt;&lt;BR/&gt;Even though I understand the rigors of maintaining a heavy symbol library, I am in favor of it. The main reason is longevity of projects. I'd like to think that if I design a product that it will still be alive and well 10 years later. If a young engineer comes in and looks at my schematic and sees that I need an op amp and thinks "oh, well I'm sure a LM741 will work fine here. It's just an &lt;A HREF="http://chrisgammell.com/2008/08/02/how-does-an-op-amp-work-part-1/" REL="nofollow"&gt;op amp&lt;/A&gt;, right?" In fact, the node the op amp is on was very sensitive and required pA of bias current and mV of offset voltage. Not only that, the young engineer also gets the part in house and realizes they have the wrong part size AND pin layout. So while I understand your argument for speed and simplicity of maintaining a library, I think designing for long term projects might convince you otherwise. Good post and one I enjoy talking about!&lt;BR/&gt;&lt;BR/&gt;Chris</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/31006871/7924235526110753457/comments/default/3582210870762771302'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/31006871/7924235526110753457/comments/default/3582210870762771302'/><link rel='alternate' type='text/html' href='http://blog.engineersimplicity.com/2008/10/light-and-heavy-components.html?showComment=1224503880000#c3582210870762771302' title=''/><author><name>Chris Gammell</name><uri>http://chrisgammell.com</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://blog.engineersimplicity.com/2008/10/light-and-heavy-components.html' ref='tag:blogger.com,1999:blog-31006871.post-7924235526110753457' source='http://www.blogger.com/feeds/31006871/posts/default/7924235526110753457' type='text/html'/></entry></feed>