Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!slug!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!ux1.cso.uiuc.edu!tank!gargoyle!chinet!patrickd
From: patrickd@chinet.chi.il.us (Patrick Deupree)
Newsgroups: comp.windows.ms
Subject: Re: Advice wanted on Windows prototyping tools
Keywords: CASE, Actor, Smalltalk
Message-ID: <1990Jun7.202442.2687@chinet.chi.il.us>
Date: 7 Jun 90 20:24:42 GMT
References: <965@ashton.UUCP>
Distribution: usa
Organization: The Whitewater Group, Evanston, IL
Lines: 40

In article <965@ashton.UUCP> tomr@ashton.UUCP (Tom Rombouts) writes:
>[Wants prototyping tool for Windows apps]
>Actor:  Designed for Windows, very compact code, but will require
>re-coding for production version.
I would, of course, recommend Actor for creating the entire app from
prototype to final application phase.  However, my opinion is somewhat
biased since I work for the company.  @:)

>CASE:W:  Generates C code based on SDK, but a fairly limited
>tool, based on a friend who used version 1.20.

If I were you I'd look at WindowsMaker as opposed to CaseW.  Neither will
generate screens for you.  They will only generate windows with a menu
that ties into dialog boxes and/or procedures that you define in C.  If this
is what you want, WindowsMaker is much better than CaseW.

>Smalltalk/V:  An established language on a variety of platforms,
>but may not be usable for production version due to royalty
>requirements and my desire to use an existing body of C code.

Keep in mind that Smalltalk produces an application that runs under a windowing
system.  It does not create a windows application, though.  It creates a window
that creates smalltalk windows within itself.  If you want something that has
the look and feel of a windows app, this wouldn't do it.  If you want an
object oriented language/environment that really kicks butt, then I'd buy
Smalltalk.

>(C++:  It is my belief that there is not enough Windows C++ code
>or classes yet available to even consider this.)

You might be right.

Don't forget about ToolBook.  If you want to create screens quickly this will
do it for you.  You can then use something like Actor to create the code
that will run in the background or that will integrate ToolBook screens.
-- 
"Organized fandom is composed of a bunch of nitpickers with a thing for
 trivial pursuit."  -Harlan Ellison

Patrick Deupree ->	patrickd@chinet.chi.il.us