kicad-developers team mailing list archive

[Manveru <manveru@...>]

--0015175ce15462ba94047ae85735 Content-Type: text/plain; charset=UTF-8

2009/12/16 vladimir_uryvaev <vovanius@...>

>
>
>
>
> --- In kicad-devel@xxxxxxxxxxxxxxx <kicad-devel%40yahoogroups.com>, Werner
> Almesberger <werner@...> wrote:
> > > Only analytic number representation can remove rounding problem
> completely. :)
> >
> > If such an ability came from retaining more context of where
> > dimensions originate, that would actually be quite useful in
> > a number of cases. It's basically what I'm trying to do in
> > fped, where the underlying math and geometry can be made
> > explicit. I think the next generation library initiatives will
> > also run into this issue before too long.
>
> Analytics brings cad more close to geometric software than to electronic.
> :)
> But I agree that some sort of them may be usable. For example is would be
> handy to store footprint generayion algorithms in library instead of tons of
> drawings of all these SOICs, SSOPs, MSOPs, QSOPs, MLFs and BGAs.
>
>
> _,_._,___
>

And that is a great idea - same I have reading all these JEDEC & IEEE
standards last week...

-- 
Manveru
jabber: manveru@...
gg: 1624001
http://www.manveru.pl
 --0015175ce15462ba94047ae85735 Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">2009/12/16 vladimir_uryvaev <span dir=3D=
"ltr">&lt;<a href=3D"mailto:vovanius@...";>vovanius@...</a>&gt;</span><b=
r><blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204=
, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">













<div style=3D"background-color: rgb(255, 255, 255);">
<span>=C2=A0</span>


<div>
<div>


<div>
=20=20=20=20=20=20
=20=20=20=20=20=20
<p></p><div class=3D"im"><br>
<br>
--- In <a href=3D"mailto:kicad-devel%40yahoogroups.com"; target=3D"_blank">k=
icad-devel@xxxxxxxxxxxxxxx</a>, Werner Almesberger &lt;werner@...&gt; wrote=
:<br></div><div class=3D"im">
&gt; &gt; Only analytic number representation can remove rounding problem c=
ompletely. :)<br>
&gt; <br>
&gt; If such an ability came from retaining more context of where<br>
&gt; dimensions originate, that would actually be quite useful in<br>
&gt; a number of cases. It&#39;s basically what I&#39;m trying to do in<br>
&gt; fped, where the underlying math and geometry can be made<br>
&gt; explicit. I think the next generation library initiatives will<br>
&gt; also run into this issue before too long.<br>
<br></div><div class=3D"im">
Analytics brings cad more close to geometric software than to electronic. :=
)<br></div><div class=3D"im">
But I agree that some sort of them may be usable. For example is would be h=
andy to store footprint generayion algorithms in library instead of tons of=
drawings of all these SOICs, SSOPs, MSOPs, QSOPs, MLFs and BGAs.<br>
<br>
</div>

</div><br></div></div><div style=3D"color: rgb(255, 255, 255); min-heig=
ht: 0pt;">_,_._,___</div>


</div>



=20=20






</blockquote></div><br>And that is a great idea - same I have reading all t=
hese JEDEC &amp; IEEE standards last week...<br clear=3D"all"><br>-- <br>Ma=
nveru<br>jabber: <a href=3D"mailto:manveru@...";>manveru@...</=
a><br>
=C2=A0 =C2=A0 gg: 1624001<br> =C2=A0 <a href=3D"http://www.manveru.pl";>htt=
p://www.manveru.pl</a><br>
 --0015175ce15462ba94047ae85735--