'k.

I've added a few words at=20
http://www.piclist.com/techref/pcbcads.htm by stealing a bit from Phil B.
and Rob Young (hope you don't mind) and finished up with the following:

At least one library that you can be confident in is the PIC library (
http://www.piclist.com/images/boards/pic.scr ) =A0created by Olin Lathrop=
 of=20
http://www.EmbedInc.com/PIC. Mr. Lathrop is a highly paid, professional
consultant, who, from time to time, shares his valuable work in the hopes
that it will be a good advertisement for his business. It contains device
definitions for 16C773, 16F876-?, 16F877-?, 16C622A-?, 16*F628-?, 12F629-=
?,
12F675-?, 18F452-?, 18*F1320-?, 18*F252-?, 16F630-?, 30F2010, 18*F6520-?,
30F6010-?, 16*F648A-?, 10F206-*/?, 30F4011-?, 10F204-*/?, 10F200-*/?,
10F202-*/?, 30F4012-*/?.

Olin: You will, of course, let me know if that is ok?

I don't use Eagle so if there are any specific instructions people should
know on using a script to build a library, perhaps someone could suggest
them?

---
James.
=20
=20

> -----Original Message-----
> From: piclist-bounces@mit.edu=20
> [mailto:piclist-bounces@mit.edu] On Behalf Of Olin Lathrop
> Sent: 2005 Apr 29, Fri 13:15
> To: Microcontroller discussion list - Public.
> Subject: Re: [EE]: question for EAGLE users
> Importance: Low
>=20
> James Newton, Host wrote:
> > Good work that is used by only one person is a waste. I.e. "a bells=20
> > not a bell till you ring it" and all that rot...
>=20
> Well, yeah, that's true, but I don't see the upside for me in=20
> giving away my libraries for free.  I've spent many hours=20
> making parts that either weren't available or too ugly or=20
> sloppily made for my standards.  I'm very picky about=20
> neatness and readability in my schematics and take some care=20
> making my Eagle packages and symbols.
>=20
> >From a global viewpoint, it does make sense for one person to make=20
> >something
> then as many people leverage that as possible.  But for this=20
> system to work there has to be an advantage that outweighs=20
> the costs for that one person to let others use his work. =20
> When there is little or no incremental production cost, we=20
> usually handle this with copyrights and licenses so that=20
> force the users to in some way compensate the originator.
>=20
> The disadvantages of giving away my Eagle libraries are:
>=20
> 1 - Even though they are just "sitting there" on the disk, it=20
> still takes effort to package them up nicely, create the web=20
> page, write the instructions, make sure the download works=20
> properly, and all the other things that everyone else will=20
> take for granted.  I'm sure you understand this better than=20
> most on this list.
>=20
> 2 - Dealing with the inevitable messages, some public and=20
> some private, about why this is like that when some other way=20
> is clearly better, and oh yes, I've got this circuit with a=20
> PIC in it, please tell me what's wrong, it's urgent the=20
> project has to work tomorrow, it's really important.  Except=20
> when you mention consulting rates it turns out it's not=20
> really *that* important after all.
>=20
> 3 - Helping potential competitors.  This is probably not that=20
> likely, but it's still something to consider.  In the end I'm=20
> in business to make money, not to run a charity.
>=20
> The advantages I see are:
>=20
> 1 - Some small amount of additional exposure for Embed Inc and myself.
>=20
> Advantage 1 seems trivially small and very unlikely to ever=20
> yield a single additional dollar.  Unlike source code, there=20
> is no reasonable way to put your name on a package or=20
> schematic symbol.  This means most people won't even be aware=20
> where they came from, which pretty much defeats the advantage.
>=20
> However, just to see how this goes, I've exported my PIC=20
> library to a script file, zipped it, and attached it to this=20
> message.  It's about 12Kbytes, so I don't know if it will=20
> make it thru the server or not.
>=20



--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist