Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!elroy.jpl.nasa.gov!hacgate!ashtate!dbase!garyc
From: garyc@dbase.A-T.COM (Gary Carter)
Newsgroups: comp.windows.ms.programmer
Subject: Re: MS-Windows Training?
Message-ID: <790@dbase.A-T.COM>
Date: 17 Nov 90 01:36:02 GMT
References: <227@stbimbo.UUCP>
Reply-To: garyc@dbase.UUCP (Gary Carter)
Organization: Ashton-Tate
Lines: 18

What I did was read Petzold's 'Programming Windows' for several hours;  then
typed in, compiled, stepped through with Codeview, and ran the first few
programs.  Then I read the SDK reference books for a few hours, then tried
out a few simple additions to one of the Petzold programs I had previously
typed in.  This got me going pretty well.

You might try doing the same thing; then read the articles in this newsgroup
and see if they make sense.  If not, try out a program from the relevant
chapter of Petzold, consult the SDK reference, and THEN see if they make
sense.  If you have already written C code for X-windows this should bring
you up to speed pretty quickly.  Also, try to find SOMEBODY who is writing
Windows code to talk to for an hour or so once in a while.

I attended a Microsoft University course in Windows, and found it pretty
slow and vanilla.  I think you'd learn a lot more following the first paragraph
above for a week, than attending the U. for a week.  I didn't feel I learned
more than one or two minor points (that I hadn't noticed, but were right
there in the SDK reference) in the whole class.