X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Injected-Via-Gmane:	http://gmane.org/
To:	geda-user AT delorie DOT com
From:	Kai-Martin Knaak <kmk AT familieknaak DOT de>
Subject:	Re: [sdb-jPU6KpCpLHWsTnJN9+BGXg AT public DOT gmane DOT org: Re: [geda-user] FOSDEM]
Date:	Wed, 11 Feb 2015 09:17:54 +0100
Lines:	25
Message-ID:	<mbf37j$9m$1@ger.gmane.org>
References:	<20150205014156 DOT GG13588 AT slana DOT eecs DOT oregonstate DOT edu>
Mime-Version:	1.0
X-Complaints-To:	usenet AT ger DOT gmane DOT org
X-Gmane-NNTP-Posting-Host:	a89-182-40-162.net-htp.de
User-Agent:	KNode/4.14.1
Reply-To:	geda-user AT delorie DOT com

Traylor Roger wrote:

> As as occasional, and fairly novice user, I found the M4 footprint
> mechanism to be baffling. I fully agree with Stuart concerning this.
> File footprints make so much sense, espeically to the beginner or
> occasional user.
> 
+1
I am neither an occasional user nor a novice. But I still never 
managed to get the hang of m4 generation. In theory it all sounds fine 
and dandy to define footprints algorithmically. But in the real world 
there are just too exceptions from whatever rule you define.

I found a hybrid approach the most practical: Use some kind of 
scripted generator to produce a footprint with all the basics. Then 
use the GUI of pcb to account for whatever exception this special case 
needs.

The same applies to symbols with large pin counts. djboxsym provides a 
box with all the required pins. I then move them around or change the 
aspect ratio and make the result more pleasing to the eye.

Just my two user cents.

---<)kaimartin(>--- 

- Raw text -