Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!decwrl!labrea!Portia!Jessica!rdsesq
From: rdsesq@Jessica.stanford.edu (Rob Snevely)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Prototyper (was: Re: New Mac Programmer -- HELP! ...)
Message-ID: <1041@Portia.Stanford.EDU>
Date: 21 Mar 89 18:53:13 GMT
References: <67@sppy00.UUCP> <169@indri.primate.wisc.edu> <3955@ece-csc.UUCP> <28672@sri-unix.SRI.COM> <13892@duke.cs.duke.edu> <7540@boulder.Colorado.EDU> <9641@burdvax.PRC.Unisys.COM>
Sender: USENET News System <news@Portia.stanford.edu>
Reply-To: rdsesq@Jessica.stanford.edu (Rob Snevely)
Distribution: na
Organization: Stanford University
Lines: 22

Hello Net-Land,

Having used Prototyper off and on for almost a year, Here are my thoughts and
opinions on it. For doing generic user-interface stuff it's ok. The code it
puts out seems more than a bit verbose, and sometimes hard to read. It does due
a main event-loop structure thats ok but I perfer mine a bit more modular. 
(this is a personal preference that others may hate). It is good for building
a prototype ( as the name inplies ). I used it to prototype a simple program
that I am working on, however I found that I needed to rewrite the event-loop
for clarity. The best thing that it does is generate resources. Thats what I 
use it for the most. A more graphical Res-Edit. So if you are a new programmer
(like me), it is a helpful tool. It won't allow you to skip inside mac and
if you want good code examples, check with another Mac programmer or maybe
the USENET guide. An ok tool (I got it at an educational Discount) but its
not the answer to my screams in the night. If you do alot of prototyping,
it might also be worth a look.
It's only my opinion. I have no connection with Smethers-Barnes except I got
an OK product at a decent price.

rob

rdsesq@jessica.stanford.edu