Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!udel!burdvax!dave
From: dave@PRC.Unisys.COM (David Lee Matuszek)
Newsgroups: comp.sys.mac.apps
Subject: Re: Easy GUI accessible through Lightspeed C?
Message-ID: <15535@burdvax.PRC.Unisys.COM>
Date: 8 Nov 90 16:54:50 GMT
References: <14369@cs.utexas.edu> <27092@cs.yale.edu> <PHILS.90Nov7095323@chaos.cs.brandeis.edu>
Sender: news@PRC.Unisys.COM
Organization: Unisys Corporation, Paoli Research Center; Paoli, PA
Lines: 26

In article <PHILS.90Nov7095323@chaos.cs.brandeis.edu> phils@chaos.cs.brandeis.edu (Phil Shapiro) writes:

>Personally, I would recommend using AppMaker (from Bowers Development)
>over Prototyper (although I *haven't* seen Prototyper v3.0).  The big
>win of AppMaker is that it can use the Think Class Library for most of
>its interface construction.  This provides code that is, IMHO, much
>easier to modify and customize, and allows the user to make a fair
>amount of interface changes without re-customizing the source code each
>time.

I don't know AppMaker and can't really compare the two.  However, you
are correct that a big problem with earlier versions of Prototyper was
"re-customizing the source code each time" you made any changes to the
user interface.  This problem has been completely resolved in
Prototyper 3.0, though--there is a clean separation between
Prototyper-generated code and user-written code.

Regarding the Think Class Library, I can't say (I've only recently
ordered my THINK Pascal upgrade, and it hasn't arrived yet).  However,
Prototyper 3.0 does generate code for the most up-to-date versions of
THINK C and THINK Pascal.

-- Dave Matuszek (dave@prc.unisys.com)
-- Unisys Corp. / Paoli Research Center / PO Box 517 / Paoli PA  19301
-- Any resemblance between my opinions and those of my employer is improbable.
< You can put a mouse on an IBM.  And you can put a radio on a motorcycle. >