X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Message-ID: <5994C2F8.7060603@xs4all.nl>
Date: Thu, 17 Aug 2017 00:11:04 +0200
From: "Bert Timmerman (bert DOT timmerman AT xs4all DOT nl) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.19) Gecko/20110429 Fedora/2.0.14-1.fc13 SeaMonkey/2.0.14
MIME-Version: 1.0
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] [pcb] mainline: redundant attributes: bug or feature?
 (fwd)
References: <alpine DOT LRH DOT 2 DOT 01 DOT 1708160810170 DOT 3058 AT homer12 DOT u DOT washington DOT edu> <d36de00d-9a5e-c856-c78c-cbe28a14122d AT fastmail DOT com> <5994AA88 DOT 1090602 AT xs4all DOT nl> <806564ad-a555-31dd-b705-e472773b445b AT fastmail DOT com>
In-Reply-To: <806564ad-a555-31dd-b705-e472773b445b@fastmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfAoI+2nXuF7Af4jZuu1SddL0jMNAFLrpOViBeV19rBZAGG0QKE4hiJY3zeBDqZzCi2qFwCcxbW6ljhjmAPddDwjayTTDVL/JgGrxcS9qXqxYK0SOftQf
 lorjVOoWxtvONoAAUo0yxMBQAfT2flKEPplgp+B9X5/SicHHmEpKzly8dEHzBRFr5iIJFeWXtKJBiQ==
Reply-To: geda-user AT delorie DOT com

Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com] wrote:
>
>
> On 08/16/2017 01:26 PM, Bert Timmerman (bert DOT timmerman AT xs4all DOT nl) [via 
> geda-user AT delorie DOT com] wrote:
>> Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com] wrote:
>>>
>>>
>>> On 08/16/2017 08:15 AM, Frank Miles (fpm AT u DOT washington DOT edu) [via 
>>> geda-user AT delorie DOT com] wrote:
>>>> On 08/14/2017 10:28 PM, Nicklas Karlsson 
>>>> (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
>>>>>> I suspect my thoughts were this: the user API should require/expect
>>>>>> unique keys (hence get-by-value) but the low level stuff should 
>>>>>> be able
>>>>>> to preserve (erroneous) redundant keys when loading/saving a 
>>>>>> *.pcb file.
>>>>>> Making load/store git friendly is a goal in pcb.
>>>>> Attribute with same name added several times may in sort of be 
>>>>> interpreted as a list of values. In gschem it is possible to add 
>>>>> several attributes with same name but it never make sense and it's 
>>>>> not possible to know for sure which value is used.
>>>> Greetings,
>>>> As a user, I might add my 2-cents to this discussion by saying that 
>>>> I use multiple instances of the "Comment" symbol attribute in my 
>>>> schematics. I would hate to see this capability be removed. Comment 
>>>> attributes to not span multiple text lines. Therefore, I need to 
>>>> add as many "Comment" attributes as I need lines of text.
>>>>
>>>> Another item may be that earlier someone posted that only the first 
>>>> instance of an attribute is used and subsequent instances are 
>>>> ignored. Why not the last instance is used and previous instances 
>>>> are ignored, as in many other configuration scripts. That way the 
>>>> latest version would be used and the system would be more 
>>>> forgiving. A warning, not an error should suffice.
>>>>
>>>> Girvin Herr
>>>>
>>>> ----------------------------
>>>>
>>>> I also make heavy use of multiple "Comment" entries for a given 
>>>> component.
>>>>
>>>> An even nicer alternative (for me) would be to enable custom 
>>>> attribute types.
>>>> Currently I use these entries to add hooks that tie entries in our 
>>>> local component
>>>> database with the schematics - a custom attribute type would be 
>>>> cleaner.
>>>>
>>>>     -Frank
>>> Frank,
>>> Actually, I think you can make up your own attribute names, if that 
>>> is what you are asking by "attribute type". I did it a while back 
>>> when I wasn't satisfied with the single "Device=" or "Value=" and 
>>> wanted more info like "Power=", "Tolerance=", etc. The attribute 
>>> name entry box is a list of attributes but it starts blank and one 
>>> can enter any name one wishes, within reason. However, gsymcheck 
>>> barfed on my new attribute names. It only supports the canned 
>>> attribute names. So, if you don't use gsymcheck, then add your own 
>>> attributes.
>>>
>>> Devs: It would be nice if gsymcheck would allow new names, or maybe 
>>> default with a warning and allow a command line option to turn such 
>>> warnings off. I would like to make a script to use gsymcheck to test 
>>> all my symbols before packaging them, but that is not possible as it 
>>> stands, because it returns non-0 on those unknown attribute errors.
>>>
>>> HTH.
>>> Girvin Herr
>>>
>> Hi Girvin,
>>
>> IIRC, adding attribute keys to a file "attribs" seems to work for me.
>>
>> I have keys like:
>>
>> footprint
>> value
>> mfg
>> mfg_PN
>> vendor
>> vendor_PN
>> price
>> documentation
>> source
>> comment
>>
>> in them.
>>
>> I hope this helps you a bit.
>>
>> Kind regards,
>>
>> Bert Timmerman.
> Bert,
> Are you saying that any attribute defined in this "attribs" file shows 
> up in the add attribute dialog list of attributes?
>
> If so, that is a good way of adding custom attributes.
> I did a system search for attribs* and got one hit:
> /usr/local/doc/geda-gaf-1.8.2/examples/gTAG/attribs
> I looked at it and has a series of attribute names, but I am not sure 
> how that applies. I will have to do some research in the docs to see 
> how I can use this.
>
> Thanks.
> Girvin
Hi Girvin,

The attributes listed in "attribs" file seems to have some influence on 
gnetlist when creating a bill of materials.

I still have to add the key name "vendor_PN" manually for they do not 
show up in the attribute dialog list ... gattrib comes in handy here ;-)

See:

http://wiki.geda-project.org/geda:faq-gnetlist

Kind regards,

Bert Timmerman.