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 Subject: Re: [geda-user] [pcb-rnd] Release 1.0.1 Date: Sat, 25 Jul 2015 21:04:50 +0200 Lines: 26 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet AT ger DOT gmane DOT org X-Gmane-NNTP-Posting-Host: a89-182-126-155.net-htp.de User-Agent: KNode/4.14.1 Reply-To: geda-user AT delorie DOT com Jason White (whitewaterssoftwareinfo- Re5JQEeQqe8AvxtiuMwx3w AT public DOT gmane DOT org) [via geda-user- Ht4Cp5ncgjRBDgjK7y7TUQ AT public DOT gmane DOT org] wrote: > Hmm. I could get used to these parametric footprints. Good work! I feel like, parametric footprint production on the fly bears some disadvantages: * Any mechanism is necessarily less transparent than footprints that just exist. It makes the access less newbie friendly. * parameters are communicated by the name of the footprint. This calls for some specialized grammar. However, many footprints also have traditional real name which does not contain any parameter. E.g. "0805", TO220 * There is an additional run time dependency. Have the wrong version of perl, python, java, whatever installed and you are screwed. Ready made footprints can be imported from somewhere else. I feel like the default library should be a simple set of ready made files. These files may or even should be produced algorithmically at compile time. ---<)kaimartin(>---