On 13/01/2011 15:48, V G wrote:
> On Thu, Jan 13, 2011 at 10:08 AM, Olin Lathrop<olin_piclist@embedinc.com>=
wrote:
>
>> I never said I hate Eagle, and I certainly don't.  I use Eagle for
>> professional designs, and don't have much of a problem with it.  You got
>> upset at Eagle because you clearly didn't spend the time to learn it, th=
en
>> complained when things didn't work how you thought they should.  Any lar=
ge
>> piece of software is going to be like that.  They aren't and shouldn't b=
e
>> optimized for the instant gratification you want.  Get over it.  I doubt
>> you'll find another package where you won't run into the same thing,
>> although the details of what exactly you'll get pissed off about will be
>> different.
>>
> That's not true at all. Diptrace gave me instant gratification that I
> wanted. It was dead simple to use and very intuitive. I don't like the wa=
y
> it does some stuff, but it NEVER frustrated me. Everything was where I
> expected it and worked how I expected it to.
>
> So far, Altium Designer is working the same way as well. Everything going=
 as
> expected. If I don't know how to do something, the documentation is very
> easy to understand, up to date, and accurate. I can't say same about
> Eagle's.
>
> Also, I'm not the only one that finds Eagle counterintuitive. But that's =
not
> the point of this thread. I'm sure it's great software for those who know
> how to use it and are accustomed to it. I am not one of those people.
I've found all instantly easy to use CAD packages ultimately very poor,=20
and the ones that take some effort vary from very good to absolute rubbish.

I have over 20 years CAD/Schematic/Layout experience and found Eagle=20
frustrating for first few days. Now I'm happy with it.
Before start finalise requirements, document. Pictures, Words, photos etc.
Look at related designs
have ideas how to do it
1) stage one sketch snippets of circuits etc and print relevant parts of=20
data sheets. Blank or squared paper depending on design type. finalise=20
design
2) Finalise chips used. Design now locked.
3) Create libraries for all chips that might be used before ANY=20
schematic entered!
4) Do schematic capture
5) Make schematic pretty and change layout more like experience suggests=20
PCB will be
6) Maybe test some bits on stripboard or manhatten/Dead bug. Rarely=20
plugin board
7) Simulations and Filter designs if needed   maybe repeat 6
8) Finalise passive parts
9) Revise Schematic
10) do something else
11) Pretty schematic some more. Usually makes bugs/errors obvious
12) Commence layout
13) Build and test section at a time
14) System test, verify against spec
15) repeat above as required

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