X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-TCPREMOTEIP: 173.48.170.224 X-Authenticated-UID: jpd AT noqsi DOT com From: John Doty Content-Type: multipart/alternative; boundary="Apple-Mail=_8DCECC40-3BCF-4A15-AB92-9479E5242F5E" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [geda-user] Proposal: Library handling Date: Wed, 19 Feb 2020 17:49:47 -0500 References:

<20200219220029 DOT 125afb8941f9ea3303eb9f93 AT gmail DOT com> To: geda-user AT delorie DOT com In-Reply-To: <20200219220029.125afb8941f9ea3303eb9f93@gmail.com> Message-Id: X-Mailer: Apple Mail (2.3273) 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 --Apple-Mail=_8DCECC40-3BCF-4A15-AB92-9479E5242F5E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Feb 19, 2020, at 4:00 PM, N (nicklas DOT karlsson17 AT gmail DOT com) [via = geda-user AT delorie DOT com] wrote: >=20 > Have seen an example a few weeks ago there someone added an attribute = to reference part and it might solve the light/heavy symbol problem. It = would be possible to add feature with a list of value for attribute = values referencing part is filtered depending on attribute values. I=E2=80=99ve done things like that, modifying footprints in netlists = based on the device=3D attribute: = https://github.com/TESScience/FPE/blob/FPE-7.0/FPE/Schematic/map-footprint= s.scm = = https://github.com/TESScience/FPE/blob/FPE-7.0/FPE/Schematic/SDPCB-footpri= nts.scm = I=E2=80=99ve also post-processed BOMs with AWK using attributes as keys = to add additional info from a database. But that still doesn=E2=80=99t = solve the problem that generic library symbols don=E2=80=99t fit the = project. These scripts can=E2=80=99t generally guess what footprint to = use without more info than a generic symbol has. John Doty Noqsi Aerospace, Ltd. jpd AT noqsi DOT com --Apple-Mail=_8DCECC40-3BCF-4A15-AB92-9479E5242F5E Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

On Feb 19, 2020, at 4:00 PM, N (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:

Have seen an example a few weeks = ago there someone added an attribute to reference part and it might = solve the light/heavy symbol problem. It would be possible to add = feature with a list of value for attribute values referencing part is = filtered depending on attribute values.

I=E2=80=99ve done things like that, modifying = footprints in netlists based on the device=3D attribute:

https://github.com/TESScience/FPE/blob/FPE-7.0/FPE/Schematic/ma= p-footprints.scm

https://github.com/TESScience/FPE/blob/FPE-7.0/FPE/Schematic/SD= PCB-footprints.scm

I=E2=80=99ve also post-processed BOMs with AWK using = attributes as keys to add additional info from a database. But that = still doesn=E2=80=99t solve the problem that generic library symbols = don=E2=80=99t fit the project. These scripts can=E2=80=99t generally = guess what footprint to use without more info than a generic symbol = has.

John Doty = Noqsi = Aerospace, Ltd.

jpd AT noqsi DOT com

= --Apple-Mail=_8DCECC40-3BCF-4A15-AB92-9479E5242F5E--