Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!husc6!think!ames!ucbcad!ucbvax!CS.UCLA.EDU!srt
From: srt@CS.UCLA.EDU
Newsgroups: comp.sys.apollo
Subject: So What's Wrong With Aegis?
Message-ID: <8706031825.AA04681@zeus.CS.UCLA.EDU>
Date: Wed, 3-Jun-87 14:25:02 EDT
Article-I.D.: zeus.8706031825.AA04681
Posted: Wed Jun  3 14:25:02 1987
Date-Received: Sun, 7-Jun-87 01:43:19 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 16

David Krowitz gave us a nice summary of some of the nice features of
Aegis.  The opposite side of the coin is:  What's wrong with Aegis?  Where
did Apollo screw up?

I'm a little dissatisfied with the Display Manager, which is very 
window-oriented.  It is easy enough to write any kind of graphics inside
a particular window, but very difficult to write anything that deals with
the screen as a whole (unless you usurp the whole screen).  To pick a 
trivial example, try and write a program that crawls a crab around the 
background portion of the display without being in borrow mode.  Or write
a program that changes the background pattern.  I also dislike the fact
that you have to specifically acquire the display (and interrupt all other
display processing) in order to perform graphics in a window.  Amongst 
other things, it can make debugging graphics code an incredible bitch.

					-- Scott