delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f |
X-Authentication-Warning: | envy.delorie.com: dj set sender to dj AT delorie DOT com using -f |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | geda-user AT delorie DOT com |
Subject: | Re: [geda-user] pinmapper filter |
In-Reply-To: | <alpine.DEB.2.00.1707310328470.27212@igor2priv> (gedau@igor2.repo.hu) |
Date: | Sun, 30 Jul 2017 21:46:02 -0400 |
Message-ID: | <xnzibl5qg5.fsf@envy.delorie.com> |
MIME-Version: | 1.0 |
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 |
My original design was like that, but in this case I have three related things: 1. The footprint 2. The pin mapping 3. The vendor/manufacturer information (attributes) I really don't want these things separated. I also found, while using it, that was easy to just edit the mapping in emacs and hit "import" in pcb. Keeping it out of the schematics means you can have two pinmappings for two different uses of the same schematic. I might consider having a one-file-per-component database somewhere that it can read, too, though, but having one file to edit while looking up parts at digikey was handy.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |