Path: utzoo!attcan!uunet!midway!ncar!hsdndev!husc6!endor!siegel
From: siegel@endor.uucp (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Scrolling lists in dialogs
Keywords: Can I get this job done really fast?
Message-ID: <5024@husc6.harvard.edu>
Date: 12 Dec 90 02:57:14 GMT
References: <2535@trlluna.trl.oz> <1990Dec11.144800.22863@midway.uchicago.edu>
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Organization: Symantec Language Products Group
Lines: 30

In article <1990Dec11.144800.22863@midway.uchicago.edu> rfl@oddjob.uchicago.edu (Bob Loewenstein) writes:

>TN 203 has some rules of thumb for using (and not using) the dialog
>manager:

	Technote 203 says lots of things, many of which are valid (e.g
"TextEdit is not a wordprocessor"), and many of which are not - I refer
specifically to the "guidelines" with respect to using the Dialog Manager.

	I invite the authors of this tech note to provide some rationale
behind their guidelines not to use the Dialog Manager in what are currently
some very valid circumstances (e.g. scrolling lists, progress indicators,
and filter procs). No justification for the guidelines is given, consequently
the technote reads: "The dialog manager is a really neat set of routines
for structured management of user-interface elements; it handles most 
common events for you, and allows you to hook into it in many useful
and convenient ways, but don't use it."

	I understand that in MacApp, modal dialogs and alerts *are* managed
using windows and views, but the world doesn't yet use MacApp, and there's
a large body of existing code that wasn't written using MacApp.

R.



 Rich Siegel	Symantec Languages Group  Internet: siegel@endor.harvard.edu

"...she's dressed in yellow, she says 'Hello, come sit next to me, you
fine fellow..."