X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Fri, 21 Aug 2015 09:04:39 +0200 (CEST)
X-X-Sender: igor2 AT igor2priv
To: geda-user AT delorie DOT com
X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From: gedau AT igor2 DOT repo DOT hu
Subject: [geda-user] [pcb-rnd] parametric footprint: plcc() and qsop()
In-Reply-To: <alpine.DEB.2.00.1508202030290.6924@igor2priv>
Message-ID: <alpine.DEB.2.00.1508210853120.6924@igor2priv>
References: <alpine DOT DEB DOT 2 DOT 00 DOT 1508191007150 DOT 6924 AT igor2priv> <alpine DOT DEB DOT 2 DOT 00 DOT 1508202030290 DOT 6924 AT igor2priv>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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

Hi all,

finished the support for plcc() and qsop() - they are just frontends to 
qf() and so() respectively. These were the last two missing generators on 
my TODO list.

Please let me know if you know of any footprint family that could be or 
should be generated. The requirements are:

- the footprint family is a series of footprints that can be generated 
using the same code, with changing some base properties (e.g. number of 
pins)

- dimensions and other properties can be calculated from the base 
properties with reasonable formulas and conditional code; e.g. sot* is not 
a good candidate for generation, as sot23 or sot89 can not be generated 
from some common anestor by varying one or two parameters, but would need 
a large table that translates package name to a pattern - easier to keep 
those in static footprint files

- has a reasonable amount of existing variations; e.g. it is not worth 
writing a generator for the dsub family because there are only a few of 
them in common use (db9, db15, db25, and maybe db37).

- preferably a link to a datasheet that shows at least 3 members of the 
family; if that's not possible, separate datasheets describing at least 3 
members of the family


Regards,

Igor2