X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=rhotlayaiHqGiL3Bm9xNt5rv+hxpEjcRGfEyK6neLzE=;
	b=h64PBo6M0Sgp+LtBn81jp3A03FpcLCzu3ynx7vVB3ytUVhnfcKtoaXeG1gTM6Q2K8k
	koKpfrmV/kcPtE8xHazlJR+DAd5nxylRvnG43y4BC4DNx9OPtjmytGfpSzFAzAMchgAA
	L3VtW0eSM/2kdYH2swe5tmM+A8xojaRZCcnLGT7UyKGE0iswsg9XDBFeL/SHDXkMKCGx
	v288YjGeb1FaJ19O/hJTsx7tc/xxam4TmfTJz2Mw8Mc00LVTAMHhzZIUWHX5N8BmQB8J
	Urr31tF5lBY0Q7LpIy8MwojvppQ58UxOTvvJj2LwMH7pTgHXFHQvLleCHVw1l3AwtBSu
	XPfw==
MIME-Version:	1.0
X-Received:	by 10.152.21.37 with SMTP id s5mr32617796lae.2.1438096460706; Tue,
	28 Jul 2015 08:14:20 -0700 (PDT)
In-Reply-To:	<mp099h$cir$1@ger.gmane.org>
References:	<CAM2RGhQ70Pex5aNeQ86vKHc7sKf_Vpws69__CPb2QKg6fJTeHg AT mail DOT gmail DOT com>
	<mnv04v$if0$1 AT ger DOT gmane DOT org>
	<0A5D410F-D1EF-4FC6-AF0F-BB13218B1615 AT icloud DOT com>
	<mo1uus$cmb$1 AT ger DOT gmane DOT org>
	<201507140318 DOT t6E3IElw031504 AT envy DOT delorie DOT com>
	<mohenr$bj9$1 AT ger DOT gmane DOT org>
	<CAM2RGhROYFyVO4oRCxKtrp9Wu5rRA42weqSq8EHwpfbPz-j3+A AT mail DOT gmail DOT com>
	<mp099h$cir$1 AT ger DOT gmane DOT org>
Date:	Tue, 28 Jul 2015 11:14:20 -0400
Message-ID:	<CAM2RGhSiz_ZdX3pfQp=TDCA9TT1xn3vyNic1sLNz_SSVRo1wtQ@mail.gmail.com>
Subject:	Re: [geda-user] The new to do
From:	"Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sat, Jul 25, 2015 at 11:17 AM, Kai-Martin Knaak <kmk AT familieknaak DOT de> wrote:
> 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?

It might be that I am misinterpreting what you are planning on doing.
I thought what you were talking about was standard triangular opamp
being populated with different pins names and numbers based on a
listing.

>  ---<)kaimartin(>---
>
>



-- 
Home
http://evanfoss.googlepages.com/
Work
http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/

- Raw text -