Mail Archives: geda-user/2016/04/10/06:06:11
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(>---
- Raw text -