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=date:from:to:subject:message-id:in-reply-to:references:mime-version
	:content-transfer-encoding;
	bh=ZivoS6udI/G+E6AAb2x44m8IHzgEbvrItpawGzgLluo=;
	b=SRNtnS0kIyo0377c3WFBJTPHZgAw/c9h+hOMPrrQg+wTPc4d6VRXFTCso2d6VQi5MC
	SMua7b7F7lEapZWV/X2ISwqZXNlYRlvWYpN66NHvbTnUHddHVcwUU6x8W7yUbeg7zz+w
	1aALr5JS7q3KVICqYXp7O6XlIB8w2OR3ufVN52VdQEGt5j45Kfm5vOFo3XOiTJVG2Fcc
	zT4GHcX2JfWguofF5k7neRAcCbpXnokCN7nUkY/a2dETdAwARsoCWwmFNhWE1CZkf+8X
	o5uqnlnMsuOya2oI4M3x/TLkFjWPlqMl3IJgVzinXuc9/3VF11P6/K1CyfUOuj7OzRWF
	1YzQ==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
	:references:mime-version:content-transfer-encoding;
	bh=ZivoS6udI/G+E6AAb2x44m8IHzgEbvrItpawGzgLluo=;
	b=XMH0MYBXEj3t0PhYEFfoya5I84hp6SexMVcKZ6iDU3+TWwDxoBnOe0smiauWhEqT1y
	wf5YL920+/KYCJRjCQgRsDqFuOjAM9vy8rr4FRC6y/glO0fDowJ6Ea1KReY5OowqdijB
	bXlsSv1G2C3V4lacgR3M4fsWOunY4rHsZFreY5rMiqz+n9ubv1rpi20CehH5e/BrtSfY
	B4DiTh9phNeMLJZWj1WMWjRmOaszJ9CSQh2evzAgNDrKJ+V8xa4PudB3JNZvclaMTx22
	k8ZMBsiUJoPDtSPJe4aZS7dVxszuk73PN3m2FsfpfbpLH5NLxdLyUuGvHqq6cBPLLc5a
	EsgQ==
X-Gm-Message-State:	AA6/9RnsrgV/qgrFpGWXLzmN6NNiuqZ6ClW45WcmicLa3/m0OF2Fwo2uy7VqwoM0mkgPnw==
X-Received:	by 10.194.126.133 with SMTP id my5mr23553652wjb.47.1474990450051;
	Tue, 27 Sep 2016 08:34:10 -0700 (PDT)
Date:	Tue, 27 Sep 2016 17:34:05 +0200
From:	"Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Possible paths of gnetlist development
Message-Id:	<20160927173405.ca856c94e3054fde7b211cb8@gmail.com>
In-Reply-To:	<83F603BB-B5A2-4332-80D4-92D31DA03949@noqsi.com>
References:	<alpine DOT DEB DOT 2 DOT 11 DOT 1609221743230 DOT 2817 AT nimbus>
	<alpine DOT LRH DOT 2 DOT 01 DOT 1609230805300 DOT 4835 AT homer03 DOT u DOT washington DOT edu>
	<9067F448-ADF3-4A04-AC40-E82A87AC2BB5 AT noqsi DOT com>
	<20160926102647 DOT 1820967e AT floyd DOT freeelectron DOT net>
	<83F603BB-B5A2-4332-80D4-92D31DA03949 AT noqsi DOT com>
X-Mailer:	Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version:	1.0
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

Yes gschem have all the flexibility neeeded then it come to attributes, just have to figure out how to best use them in a standardardized way.


On Tue, 27 Sep 2016 09:54:27 -0400
John Doty <jpd AT noqsi DOT com> wrote:

> 
> On Sep 26, 2016, at 10:26 AM, al davis <ad252 AT freeelectron DOT net> wrote:
> 
> > On Mon, 26 Sep 2016 09:05:21 -0400
> > John Doty <jpd AT noqsi DOT com> wrote:
> >> 1. Use attributes for rather than special backend-dependent symbols
> >> like spice-subcircuit-LL.
> > 
> > I agree.
> > 
> > Likewise, backends should not have anything symbol-specific.
> 
> There’s nothing symbol-specific in gnetlist. A back end can’t even find out which symbol(s) a “package” corresponds to. But spice-subcircuit-LL.sym has the attribute device=spice-subcircuit-LL, which the SPICE back ends recognize. The problem here is that the layout back ends think this is an actual component.
> 
> > 
> > and all backends should support attributes, in a consistent way.
> > 
> 
> The trouble here is that gEDA supports an open-ended variety of flows, and one size does not fit all. Every gnetlist back end uses the footprint attribute, but what should you put in it? The names from your layout tool’s library? The gEDA convention (http://wiki.geda-project.org/geda:pcb_footprint_naming_conventions, mischievously presented as a pcb convention)? If you use the gEDA convention, do you alias the footprints in the library to match, or do you automatically translate? A lot depends on the size of the project, the tools employed, and the skills and preferences of the designer(s). I’ve used every one of these approaches for one project or another.
> 
> If you’re simulating with SPICE, you’ll want your numeric value attributes to be SPICE numbers. Fortunately, procurement folks find this usable in a BOM. But for a different flow, you might want something different.
> 
> Then, there are attributes for specific back ends. Some of the standard library symbols have pins and class attributes for Allegro. The class attribute is probably not useful for any other flow, but I find pins useful for DRC (http://www.gedasymbols.org/user/john_doty/tools/check-pincount.html).
> 
> 
> John Doty              Noqsi Aerospace, Ltd.
> http://www.noqsi.com/
> jpd AT noqsi DOT com

- Raw text -