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=fastmail.com; h=
	content-transfer-encoding:content-type:date:from:in-reply-to
	:message-id:mime-version:references:reply-to:subject:to
	:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=QjAmP/
	MwSmqX/ZJOKED8uWsYbnumZboXTljkbH5NJ2E=; b=OcgI9CL2Nv07SG7bwP4O1J
	Z4jPTj6C5C7fo36bNgNc/i7HVZ5bYHBV0opdererEmAh52E9M6HPWd1ENrCwhcov
	OtuWTyBsdIkcObvSjwHLz90+Qldfxr8GrWtOjcccOXjGs1iRoYoEfljMbcAsfcny
	e+p4csnCBTgKW3bjbXt0qSJpCrifSdGGlYy+Igr6J7wIE6Bo3UDLIC5mTQYeb/nt
	Xxwr7CUDDQ2y3WRnZJfj6nSgQWGJIZKljmNkRZ60jG/KKvoJas0zUWwCo1QuMbxu
	8Yl6+a4fsmSrHRFHZDWhj5OlDxO6L05KZgphsdH73SjjdaoZscRpmeg9/qsrdd9Q
	==
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=content-transfer-encoding:content-type
	:date:from:in-reply-to:message-id:mime-version:references
	:reply-to:subject:to:x-me-sender:x-me-sender:x-sasl-enc
	:x-sasl-enc; s=fm1; bh=QjAmP/MwSmqX/ZJOKED8uWsYbnumZboXTljkbH5NJ
	2E=; b=RSJTbh59gwe/1bK0frgbJ81Cuo7Vtre48Bns3sReiXrPOsX5TPD8xnQ+G
	wzhmSvNw58hMxMn+bIEHSN+h5Uv98acCWCjYBeq8YHeNW9agCpY+GlA0c7Hw/y9k
	t8OxH0ktG6LxwLqUPy0IoL/wyt+vS5XLo0P7gYLYjjS4NfYBMShUsJTT7HMk4ZiW
	guicPFe2LfZziw4Rm2Hhd38blscoNaXiK/yBcll0C1weNtqmFjKLzLNMYvlmCAOk
	5n4aYr+NPxLntaCoWKxPtbdynwPVLe6EHEW6FcyfWdLjXpwpOHrWnR7K3tG0Oxeq
	GVxfg6Kg5X7Mv8p0WxJsbyJBA8A+Q==
X-ME-Sender: <xms:T9mUWW4VUCBBnj5Dm6Vsz2I_u3uuUjp9n_fPhiYytkW-OdhWrNXGvg>
X-Sasl-enc: +juIxl9ObYHgKIbBnzEBStZU/ASNZfPfN5m6Yl8uhyvK 1502927182
Subject: Re: [geda-user] [pcb] mainline: redundant attributes: bug or feature?
 (fwd)
To: geda-user AT delorie DOT com
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>
 <5994C2F8 DOT 7060603 AT xs4all DOT nl>
From: "Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID: <3638640a-df24-e804-5fc5-6bfd9ee75099@fastmail.com>
Date: Wed, 16 Aug 2017 16:40:13 -0700
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101
 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <5994C2F8.7060603@xs4all.nl>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
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
Precedence: bulk



On 08/16/2017 03:11 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 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.
Bert,
Ahhh! Yes, I remember that now. I was going to mention that the attribs 
file determines what gets printed in the BOM, but I haven't used it for 
so long I wasn't sure and the only files I could find in my account were 
ATTRIBS.LST PCAD files, which perform a similar function in PCAD. I 
thought gschem had a similar feature. Thanks for clearing that up.
Girvin