X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=seznam.cz; h=Received:From:To:Subject:Date:Message-Id:References:Mime-Version:X-Mailer:Content-Type; b=BUOc0MkEUjqkSiZ8pLmRACGOs84oVekLHbGspSt/jd9fFC+jFIftEqMgOSN2FYL8f NizaCO1PB2Twzgs4PJDbGRi9H7Vmi+IGdaBAgvUDRxARtEdkwG7iYaCaeziDWWE80Sr cCg6+DC8DJIHdc9iraZS3+beJp/tieaPSYIJBcA= From: "Vaclav Peroutka (vaclavpe AT seznam DOT cz) [via geda-user AT delorie DOT com]" To: Subject: Re: [geda-user] The new to do Date: Tue, 14 Jul 2015 15:29:37 +0200 (CEST) Message-Id: References: <0A5D410F-D1EF-4FC6-AF0F-BB13218B1615 AT icloud DOT com> Mime-Version: 1.0 (szn-mime-2.0.4) X-Mailer: szn-ebox-4.4.281 Content-Type: multipart/alternative; boundary="=_5261236c1908f80718824dd7=6aa5b07b-cb9c-51fa-b61b-ca52bdce6166_=" Reply-To: geda-user AT delorie DOT com --=_5261236c1908f80718824dd7=6aa5b07b-cb9c-51fa-b61b-ca52bdce6166_= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable =0A= "> And of course, my personal favorite:=0A= > =0A= > * the notion of "packages", a container format for all information on = =0A= > a component. E.g. symbol(s), footprint(s), value(s), spice model, 3D = =0A= > models, notes, data sheets, ...=0A= =0A= Actually, that=E2=80=99s one of the things about Eagle I really dislike. I= like =0A= separation between footprints and symbols.=0A= =0A= "=0A= =0A= =0A= =0A= I have the library of components which I have in my shack together with = =0A= ordering numbers from several vendors - TME, Farnell etc. For me the best = =0A= way to design something is to use only components from that library. I had= =0A= several times drawn something and later I found that some components can n= ot=0A= be ordered. Or I used generic NPN transistor with generic SOT23 footprint = =0A= and pins did not match. So I did my work twice. What is the beauty in such= =0A= approach to have separated everything ?=0A= =0A= =0A= =0A= ""= --=_5261236c1908f80718824dd7=6aa5b07b-cb9c-51fa-b61b-ca52bdce6166_= Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
> And of course, my personal favorite:
&= gt;
> * the notion of "packages", a container format for all inform= ation on
> a component. E.g. symbol(s), footprint(s), value(s), spi= ce model, 3D
> models, notes, data sheets, ...

Actually, tha= t=E2=80=99s one of the things about Eagle I really dislike. I like separa= tion between footprints and symbols.


I h= ave the library of components which I have in my shack together with order= ing numbers from several vendors - TME, Farnell etc. For me the best way t= o design something is to use only components from that library. I had seve= ral times drawn something and later I found that some components can not b= e ordered. Or I used generic NPN transistor with generic SOT23 footprint a= nd pins did not match. So I did my work twice. What is the beauty in such = approach to have separated everything ?


= --=_5261236c1908f80718824dd7=6aa5b07b-cb9c-51fa-b61b-ca52bdce6166_=--