🚀 go-pugleaf

In article <10584@bsu-cs.bsu.edu> mithomas@bsu-cs.UUCP (Michael Thomas Niehaus) writes:
>Someone should write an APPLICATION somewhat like Backgrounder that just
>sits and waits for incoming messages.  When a message does come, the
>Notification Manager should be used to notify the user that a message
>is waiting.  They should then have to switch to that application to
>read the message (or to send a message).  This prevents "rude interruptions"
>of the current foreground application.
>Any other opinions?
>-Michael

Well, I believe the problems in BroadCast are caused by bugs in the software,
and are not inherent to the practice of "rude interruptions."  Just as
an example, another program that interrupts whatever you're doing when it
deems necessary is Vaccine (and Gatekeeper as well).  They have *never*
crashed on me.  It should be possible, then, to modify Broadcast so that
it uses a similar mechanism to these programs when putting up the dialog
box with the message.  I don't think a separate program is needed.  This
forces you to use MultiFinder/System7 (when it comes out).  That's not
a reasonable alternative for a lot of people with 1Meg macs - not everyone
has 2M+...

Of course, a separate program using an identical communications protocol should
be available for the ones who are using MultiFinder/Sys7, and work as Mike
described.  But MF/Sys7 shouldn't be a prerequisite for message sending
ability over AppleTalk - it should be able to be implemented bug-free.

Just my $.02

-Ivan Cavero Belaunde

	"If Cerebus had a navel, would you drink Apricot brandy out of it?"

Internet: captkidd@ATHENA.MIT.EDU