[109] in Athena User Interface

home help back first fref pref prev next nref lref last post

Re: RFC: Prioritized AUI component list

daemon@ATHENA.MIT.EDU (Brad Thompson)
Mon Jun 5 15:08:41 2000

Message-Id: <200006051908.PAA02107@alice-whacker.mit.edu>
To: "Christopher D. Beland" <beland@MIT.EDU>
Cc: aui@MIT.EDU
In-Reply-To: Your message of "Mon, 05 Jun 2000 04:31:38 EDT."
             <200006050831.EAA21987@No-Whammies.mit.edu> 
Date: Mon, 05 Jun 2000 15:08:22 -0400
From: Brad Thompson <yak@MIT.EDU>

>  - Triage dotfile configuration questions

What do you mean by "triage"?

On the component list:

We should start an initial xterm.  This _is_ unix.  Inexperienced users
will make it go away, and we have session management to make it stay away.
But damnit, users should be able to log into a unix machine, type "ed",
and begin work.

***

We should differentiate the goals of aui and unix-dev.  We should
take on this whole thing in very small chunks, to keep ourselves from
getting hurt.  For example, I do not think we should even touch Console,
mail readers, xlogin, discuss, moira, office software, or any applications
not crucial to the deploy of aui until aui is pretty much done.

As far as I am concerned, we need to get panel, sawfish, and a file
manager in working condition before all else.  If these three things
are working, and nothing else is, we will have accomplished something.
If these three things are almost done, and we have a bunch of nifty apps
to go with them when we are done, no one will give a damn.

I think there is a tendency to say "X is wrong with Athena's user
interface.  AUI is working to fix Athena's user interface.  Therefore,
AUI should fix X."  If we buy into this, then we will never ship.

yak

home help back first fref pref prev next nref lref last post