Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!decwrl!ucbvax!dewey.soe.berkeley.edu!oster
From: oster@dewey.soe.berkeley.edu (David Phillip Oster)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Prototyper
Summary: Beware!
Message-ID: <28495@ucbvax.BERKELEY.EDU>
Date: 22 Mar 89 09:34:48 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> <1041@Portia.Stanford.EDU>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: oster@dewey.soe.berkeley.edu.UUCP (David Phillip Oster)
Distribution: na
Organization: School of Education, UC-Berkeley
Lines: 21

Beware of Prototyper! As a macdraw-y environment for creating user 
interfaces, you can do most of what it does using Resedit and MacDraw
(paste those picts into your dialogs for things like bracketing boxes
around groups of buttons.)

The code that it generates is not only so verbose it is hard to read
(for example, each menu item in a .r file has a useless comment:

File		;;Menu title
  New/n		;;menu item
  Open/O	;;menu item

) it is also wrong: the code generates app1 events. Under multifinder, 
since there is one global event queue, these events stand a good chance
of being delivered to some other application. If it was also written
with prototyper, it will misbehave, and so will your application, since
it isn't seeing the events it needs.

--- David Phillip Oster            --"When we replace the mouse with a pen,
Arpa: oster@dewey.soe.berkeley.edu --3 button mouse fans will need saxophone
Uucp: {uwvax,decvax}!ucbvax!oster%dewey.soe.berkeley.edu --lessons." - Gasee