Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!amdcad!ames!ncar!husc6!bloom-beacon!apple!lsr
From: lsr@Apple.COM (Larry Rosenstein)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Changing complicated Dialogs into Windows (TechNote 203)
Message-ID: <18456@apple.Apple.COM>
Date: 8 Oct 88 16:21:11 GMT
References: <4209@polya.Stanford.EDU> <10050021@eecs.nwu.edu> <713@lts.UUCP>
Organization: Advanced Technology Group, Apple Computer
Lines: 26

In article <713@lts.UUCP> amanda@lts.UUCP (Amanda Walker) writes:
>programming effort goes.  The biggest advantage of using the Dialog Manager
>is that you can use things like ResEdit to design and/or customize the
>dialog's appearance.  If you're doing everything yourself, you don't
>
>Another approach, which is most useful for people who are working in Pascal,
>is to use Prototyper from Smethers-Barnes.  Yes, it has a few bugs, but

MacApp 2.0 takes the approach mentioned in the Tech Note.  For anything
other than a simple alert, it doesn't use the Dialog Manager at all.

Instead, there are individual view objects for each of the elements that can
be put into a dialog.  This not only includes the usual things (buttons,
check boxes, etc.) but also other things such as popup menus, icons,
pictures, and clusters.  (The latter are usefule because any radio buttons
inside a cluster are made mutually exclusive automatically.)

The layout of these dialogs is stored in a 'view' resource.  There is an
alpha release of a program that lets you create these resources
interactively. 

		 Larry Rosenstein,  Object Specialist
 Apple Computer, Inc.  20525 Mariani Ave, MS 46-B  Cupertino, CA 95014
	    AppleLink:Rosenstein1    domain:lsr@Apple.COM
		UUCP:{sun,voder,nsc,decwrl}!apple!lsr