Mail Archives: geda-user/2015/07/25/17:41:41
--047d7b4725ee0053b7051bb9fad8
Content-Type: text/plain; charset=UTF-8
Kaimartin,
Counterpoints:
* Parametric footprints can be saved. This feature compliments your
standard library, not detracts from it.
* Parametric footprints makes PCB more accessible. For new users the
process of creating one's own footprints can be quite daunting.
* Great potential to reduce library clutter, duplication, and maintenance.
This makes generating footprints for custom connectors (ie. common 0.156in
headers) painless and more or less instant. That sort of flexibility is
downright useful regardless of how it was implemented.
- Aside 1: believe it or not we get new users every day, it just that when
they see the tools, they tend to run away...
- Aside 2: It seems like everyone who actually needs to use PCB on a daily
basis has their own custom fork. Igor2 has been kind enough to share his
flavor of PCB, be kind to him.
On Sat, Jul 25, 2015 at 3:04 PM, Kai-Martin Knaak <kmk AT familieknaak DOT de>
wrote:
> 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(>---
>
>
--
Jason White
--047d7b4725ee0053b7051bb9fad8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div>Kaimartin,<br><br></div><div>Counterpoints:<br><=
/div><div>* Parametric footprints can be saved. This feature compliments yo=
ur standard library, not detracts from it.<br></div><div>* Parametric footp=
rints makes PCB more accessible. For new users the process of creating one&=
#39;s own footprints can be quite daunting.<br></div><div>* Great potential=
to reduce library clutter, duplication, and maintenance.<br></div><div><br=
>This makes generating footprints for custom connectors (ie. common 0.156in=
headers) painless and more or less instant. That sort of flexibility is do=
wnright useful regardless of how it was implemented.<br><br><br></div><div>=
- Aside 1: believe it or not we get new users every day, it just that when =
they see the tools, they tend to run away...<br></div><br><br>- Aside 2: It=
seems like everyone who actually needs to use PCB on a daily basis has the=
ir own custom fork. Igor2 has been kind enough to share his flavor of PCB, =
be kind to him.<br><br></div><br></div><div class=3D"gmail_extra"><br><div =
class=3D"gmail_quote">On Sat, Jul 25, 2015 at 3:04 PM, Kai-Martin Knaak <sp=
an dir=3D"ltr"><<a href=3D"mailto:kmk AT familieknaak DOT de" target=3D"_blank"=
>kmk AT familieknaak DOT de</a>></span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">Jason White (whitewaterssoftwareinfo-<br>
<a href=3D"mailto:Re5JQEeQqe8AvxtiuMwx3w AT public DOT gmane DOT org">Re5JQEeQqe8Avxti=
uMwx3w AT public DOT gmane DOT org</a>) [via geda-user-<br>
<span class=3D""><a href=3D"mailto:Ht4Cp5ncgjRBDgjK7y7TUQ AT public DOT gmane DOT org"=
>Ht4Cp5ncgjRBDgjK7y7TUQ AT public DOT gmane DOT org</a>] wrote:<br>
<br>
> Hmm. I could get used to these parametric footprints. Good work!<br>
<br>
</span>I feel like, parametric footprint production on the fly bears some<b=
r>
disadvantages:<br>
<br>
* Any mechanism is necessarily less transparent than footprints that<br>
just exist. It makes the access less newbie friendly.<br>
<br>
* parameters are communicated by the name of the footprint. This calls<br>
for some specialized grammar. However, many footprints also have<br>
traditional real name which does not contain any parameter. E.g.<br>
"0805", TO220<br>
<br>
* There is an additional run time dependency. Have the wrong version<br>
of perl, python, java, whatever installed and you are screwed. Ready<br>
made footprints can be imported from somewhere else.<br>
<br>
I feel like the default library should be a simple set of ready made<br>
files. These files may or even should be produced algorithmically at<br>
compile time.<br>
<br>
---<)kaimartin(>---<br>
<br>
</blockquote></div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail_sig=
nature">Jason White</div>
</div>
--047d7b4725ee0053b7051bb9fad8--
- Raw text -