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 <kmk AT familieknaak DOT de>
Subject: Re: [geda-user] gschem attribute list, value list
Date: Sun, 10 Apr 2016 12:04:49 +0200
Lines: 42
Message-ID: <ned8g1$d6e$1@ger.gmane.org>
References: <20160324143854 DOT 1a1535a687a8c9fc7ff0bd01 AT gmail 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-96-67.net-htp.de
User-Agent: KNode/4.14.10
Reply-To: geda-user AT delorie DOT com

Nicklas Karlsson wrote:

> For symbol attributes there is a list of attributes to chose from
> then selecting an attribute, although manual entering is also
> possible. It would be good with list of attribute values also.
> First
> step would be possibility to store information in symbol. It is
> useful for values for in particular: resistors, capacitors and
> inductors but also for comparators, operational amplifiers and
> others.

Ack.
The symbols of my gschem libraries include an attribute "footprints"
with a comma separated list of suggested footprints. Similarly, 
they may contain an attribute "values" with a list of preferred 
values. The GUI could present these list attributes as a drop-down 
list for the user to choose from.

See
http://www.gedasymbols.org/user/kaimartin_knaak/essential/essential.html
section "List attributes"

 
> Some attribute values depend on downstream tools like footprint and
> maybe device so they be harder to get into gschem, ideally maybe
> they should be generated by downstream tool?

Ideally, the allocation of footprints should be driven by, or at least
aided by some sort of library. The advantage of a library over a generic
data base type of approach would be the ability to share. It is much more
straightforward to distribute items of a library than to clone parts of
a relational data base.

Obviously, the format of gschem symbols is not geared toward representing
all the aspects a library designer may associate with an electronics 
component. The lists of values mentioned above are already a stretch.
IMHO, a good solution would be a container format "package" which would
be specifically designed to take all these bits of information connected
to what could be loosely referred to as a "component". The information may 
be referenced or it may be explicitly contained.

---<)kaimartin(>---