Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!wa4mei!nanovx!msa3b!kevin
From: kevin@msa3b.UUCP (Kevin P. Kleinfelter)
Newsgroups: comp.windows.ms.programmer
Subject: Re: CASE tools for Windows development
Message-ID: <1566@msa3b.UUCP>
Date: 11 Mar 91 13:47:22 GMT
References: <16790.27d926a8@ul.ie>
Organization: Dun and Bradstreet Software, Inc., Atlanta, GA
Lines: 31

oreillyj@ul.ie writes:

>[...know anything about Case:W or alternatives? ...]

I'm using Case:W, "Corporate Edition V3.1."  I consider it a useful
tool.  It seems to work fairly well.

It is not a "do everything" tool. You can get it it generate the
menu bar for a "primary window", but you can't use it to design the
primary window itself.  Their method for designing the primary window
is for you to use Case:W to design the menu bar, use the dialog
editor to create a dialog, and then it creates the main window
based upon the dialog.      

It does generate a makefile, a .DEF file, etc.  I consider it useful
for creating the initial shell of a program.  Most of the time, you
can go in and modify the initial shell, and future "re-generations"
of the shell will preserve your modifications.  (However, if you modify
the dialog that the main window is based upon, you may loose your
modifications to the code that processes main window controls.)

In summary, it is a useful tool, much like make, lex, and yacc are
useful tools.  I expect it to shave a few percent off my development efforts.
I do not expect it to cut my development time in half.

It works.  This seems to be unusual in the Windows development world.
-- 
Kevin Kleinfelter @ Dun and Bradstreet Software, Inc (404) 239-2347
{emory,gatech}!nanovx!msa3b!kevin

Look closely at the return address.  It is nanovx and NOT nanovAx.