Xref: utzoo comp.windows.ms:416 comp.windows.news:1236 comp.windows.misc:1092
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucdavis!iris!chow
From: chow@iris.ucdavis.edu (John L. Chow)
Newsgroups: comp.windows.ms,comp.windows.news,comp.windows.misc
Subject: Application development using Microsoft Windows
Message-ID: <3884@ucdavis.ucdavis.edu>
Date: 4 Apr 89 07:02:13 GMT
Sender: uucp@ucdavis.ucdavis.edu
Reply-To: chow@iris.ucdavis.edu (John L. Chow)
Distribution: usa
Organization: U.C. Davis - Department of Electrical Engineering and Computer Science
Lines: 27

I am in the process of making the decision of using Microsoft
Windows as a standard user interface platform for all application
development under MSDOS.  However, I have heard mixed feelings about 
MS Windows from a few people.  Some think that it is a very complex 
windowing environment to program in.  Others don't think it is going 
to be a industrial standard for PC DOS environment.  While some
like the predefined and consistent user interface environment, there
are others who think it is too limited and not flexible if you want
to create your own user interface environment.  

Could some of you please give me your suggestion/advise based on your 
experience with MS Windows?  In addition, I would also like to know:

1. What is the future of MS Windows as a standard for DOS?
2. What are the best reference books on programming MS Windows?
3. Any comments about Glockenspiel's CommonView using C++ for Windows
   programming?
4. How complex is it for a normal C programmer to learn and use it for
   a major program development?  Is taking a class to learn about MS 
   Windows a good idea?  Who offers the best class?
5. What are other alternatives (i.e., NewWave) if MS Windows is not 
   recommended?

Thank you very much in advance for your suggestions.

-- John Chow
   chow@iris.ucdavis.edu