X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Injected-Via-Gmane: http://gmane.org/ To: geda-user AT delorie DOT com From: Kai-Martin Knaak Subject: Re: [geda-user] The new to do Date: Sat, 25 Jul 2015 17:17:05 +0200 Lines: 23 Message-ID: References: <0A5D410F-D1EF-4FC6-AF0F-BB13218B1615 AT icloud DOT com> <201507140318 DOT t6E3IElw031504 AT envy DOT delorie DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet AT ger DOT gmane DOT org X-Gmane-NNTP-Posting-Host: a89-182-126-155.net-htp.de User-Agent: KNode/4.14.1 Reply-To: geda-user AT delorie DOT com Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: >> A sufficiently versatile package format would provide a solution to >> this problem. A package can be viewed as a way to integrate the >> knowledge about the various aspects of components. >> >> A package can be as simple as a set of symbols and footprints. In >> this case the knowledge would be the implicit statement that these >> symbols and footprints are compatible. But it can also provide a >> list of footprints which can be combined with a specific symbol. It >> can also provide the information that a component needs to be >> represented by a set of symbols (e.g. a opamp could be represented >> by a triangle symbol and a separate supply symbol) > > What about opamps that have more involved pinouts? For example I > have some instrumentation opamps that are really involved. I don't quite get what you are aiming at. Can you give an example for such a component? ---<)kaimartin(>---