Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!lll-winken!uunet!mnemosyne.cs.du.edu!isis.cs.du.edu!ebergman
From: ebergman@isis.cs.du.edu (Eric Bergman-Terrell)
Newsgroups: comp.windows.ms.programmer
Subject: Re: DOS to Windows
Keywords: soliciting advice and references
Message-ID: <1991Apr20.024602.29466@mnemosyne.cs.du.edu>
Date: 20 Apr 91 02:46:02 GMT
References: <13728@alfred.Teknowledge.COM>
Sender: usenet@mnemosyne.cs.du.edu (netnews admin account)
Reply-To: ebergman@isis.UUCP (Eric Bergman-Terrell)
Organization: Nyx, Public Access Unix (sponsored by U. of Denver Math/CS dept.)
Lines: 23
Disclaimer1: Nyx is a public access Unix system run by the University of Denver
Disclaimer2: for the Denver community.  The University has neither control over
Disclaimer3: nor responsibility for the opinions of users.


Well I'm right in the middle of a port of a DOS application to Windows 3.0.

My program has a lot of code, but few large data structures, so I don't have
much advice that isn't already said better in Petzold - actually I do - if
you have static data structures that aren't too big (maybe < 32k) consider
making them RCDATA or user-defined resources (then you don't have to write
much code to load them from disk).

BTW the best part of a Windows port is throwing away all the @#$@#$ hand-
crafted menu & dialog box management code as well as the @#$@$ home-grown
printer drivers!

Also:  I am beginning to believe that the complexity of Windows application
development is rather exaggerated.  The time I've spent learning Windows
& the message passing paradigm is much less than I'd spend writing all the
things already built into Windows (e.g. on-line help)...


My $0.02


Terrell