X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Thu, 2 Apr 2015 11:43:48 -0700 From: Larry Doolittle To: geda-user AT delorie DOT com Subject: Re: [geda-user] PCB and gschem libraries Message-ID: <20150402184348.GA26113@recycle.lbl.gov> References: <03E9613B-CE78-4133-975E-D6DE0F5BE6CB AT noqsi DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <03E9613B-CE78-4133-975E-D6DE0F5BE6CB@noqsi.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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 John - On Thu, Apr 02, 2015 at 12:11:24PM -0600, John Doty wrote: > Useful, but the needs are so vastly greater than the sources could ever cover that there, too, you’re generally just looking for something that can save you starting from scratch. You’re still going to need to edit it in most cases. Background: I use and like Darrell Harmon's footgen, and DJ Delorie's djboxsym. Years ago, I put together the qfp-ui TCL/M4 scripts that might still exist in PCB. You can see I'm a fan of parameterized footprints, although they clearly have limitations and shouldn't be the _only_ thing around. What I do wish for is a better sense of building from related parts, without cutting and pasting. The footgen way is too linear for that. It would be better for some part's description to say "just like part X, but with an exposed paddle 3.6 x 3.6 mm". Somebody else could come along as and say "just like part X, but with toe increased by 0.8 mm". Managing (version-controlling) the chain of dependencies would require some thought. And coming up with a final .fp file at the end is essential, even if the usual UI flow made it virtual by way of a *nix pipe. - Larry