[331] in Zephyr_Comments
accidentally killing zephyrgrams
daemon@ATHENA.MIT.EDU (Joe Harrington)
Fri Jul 7 17:38:44 1989
Date: Fri, 7 Jul 89 17:36:37 EDT
From: Joe Harrington <jh@ATHENA.MIT.EDU>
To: mar@ATHENA.MIT.EDU, janson@ATHENA.MIT.EDU
Cc: zephyr-comments@ATHENA.MIT.EDU, athena-ws@ATHENA.MIT.EDU
In-Reply-To: <mar@ATHENA.MIT.EDU>'s message of Thu, 22 Jun 89 17:05:14 -0400 <8906222105.AA19782@TOTO.MIT.EDU>
Cc: jh@ATHENA.MIT.EDU
Reply-To: jh@ATHENA.MIT.EDU
I've been away, so I just got the zgram-time-to-live mail.
I think time-to-live is the wrong solution to misclicks (clicking away
a message that is just coming in instead of the one under it), because
I think putting new zgrams on top was the wrong solution. Zgrams
should be stacked in chronological order (i.e. new ones arrive at the
BOTTOM of the stack). That way, if you are away from your machine for
a little while, you don't have a backwards conversation to read. Your
clicks don't accidentally nuke incomming zgrams. There is no reason
for a close box other than the whole zgram. Athena doesn't have to
write fancy title-and-close-box-avoidance code which could potentially
cover the screen (instead of making a deep stack) with zgrams if some
user is being inconsiderate and znuke-ing you. I realize that some
messages are important to see NOW -- that's what instance URGENT
messages should be for. zwgc ought (I think) to allow putting the
zgram on top or on the bottom, and the default .zephyr.desc file
should put all but URGENT, OPERATIONS, and the like on the bottom.
Ideally, we should implement a place-in-position command with
an (x,y,z) coordinate as an argument, where x and y are positional X
geometry specs, and Z is one of T or B for top or bottom. This would
allow sorting of zgrams by class, sender, instance, etc.
Thoughts?
--jh--
