Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!nrl-cmf!ukma!rutgers!ucsd!orion.cf.uci.edu!tmyers
From: tmyers@orion.cf.uci.edu (Tracy Myers)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Prototyper opinions?
Message-ID: <1446@orion.cf.uci.edu>
Date: 11 Feb 89 20:24:34 GMT
References: <9128@burdvax.PRC.Unisys.COM> <3635@geaclib.UUCP> <3768@tekig5.PEN.TEK.COM>
Reply-To: tmyers@orion.cf.uci.edu (Tracy Myers)
Organization: University of California, Irvine
Lines: 19

In article <3768@tekig5.PEN.TEK.COM> danm@tekig5.PEN.TEK.COM (Daniel Milliron) writes:
>
>
>But wait, there's an added bonus.  With Prototyper, you get to experiment with
>user interface options at a speed that is at least an order of magnitude
>greater than if you were hand-coding and using some other resource editor.
>
>Dan Milliron
>
I have just received my prototyper upgrade, and have not had enough time
with it to form an informed opinion of v2.0.  But, so far so good.  I have 
found Prototyper to be a very effective tool in learning how to handle the user
interface stuff.  Instead of getting one of the canned examples that come
with every development system, you can make your own.  Want to find out
how to do radio buttons? Just do a prototype and generate the code. You can
have exactly what you want in the program (within the limits of 
Prototyper).  You don't have to wade through a large example to find the code
you are interested in.  The code is pretty thuroughly commented and easy 
to follow.  It has been very helpful in my effort to learn the interface.