Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!ut-sally!im4u!rutgers!ames!lll-tis!ptsfa!hoptoad!academ!uhnix1!sugar!peter
From: peter@sugar.UUCP (Peter da Silva)
Newsgroups: comp.sys.amiga
Subject: Re: Does RAM: ever retry?
Message-ID: <653@sugar.UUCP>
Date: Sat, 5-Sep-87 20:49:53 EDT
Article-I.D.: sugar.653
Posted: Sat Sep  5 20:49:53 1987
Date-Received: Wed, 9-Sep-87 05:42:48 EDT
References: <510@sugar.UUCP> <6619@eddie.MIT.EDU> <535@sugar.UUCP> <6756@eddie.MIT.EDU>
Organization: Sugar Land UNIX - Houston, TX
Lines: 27
Summary: Why use a requestor?


> [ it takes 60K free to reliably open a requestor ]

Why use a requestor?

I mean... what is the whole purpose of requestors? What do they do for you
that just rendering into a smart refresh window doesn't? They're a little
easier to code (not much, though, since you have to open a window for them
in the first place), but they can't be handled by the user as a first-class
object (you can open a window that has that capability, true, and most
everyone does... but then you get back to "you're opening the window anyway"),
and they take up a bunch of contiguous memory (a smart refresh window can be
diced into teeny chunks). And they're not very versatile.

I can see that they save some hassles, but in this case why don't you just
open up a window and render into it? You can even make it simple-refresh
and save even more memory!

Even better... open a 1 bit-plane lores screen that looks like an alert but let
the user click into the workbench window, pull it up, work in it, and then
pull it down and click in the right or left half of the "alert"? I'll bet
you'll save gobs of memory!

Smart alerts... what a concept!
-- 
-- Peter da Silva `-_-' ...!seismo!soma!uhnix1!sugar!peter
--                 'U`  <-- Public domain wolf.