[6781] in Athena Bugs
re: dashboard
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Thu Jan 3 13:21:38 1991
From: cfields@ATHENA.MIT.EDU
Date: Thu, 3 Jan 91 13:21:14 -0500
To: jcb@ATHENA.MIT.EDU
Cc: bugs@MIT.EDU
In-Reply-To: [6773]
> 1) there is no way to kill programs started from the menu.
In general, the programs started from the menu are independent
processes, and dash currently provides no way to kill them. However,
they should have their own quit options, or at worst you can use the
window-manager delete window or kill window options. (Use delete
window on anything of dash's, like its clock. Otherwise all of dash
will die.)
> 2) the clock menu option does not look at .Xresources for xclock.
True. The clock is not xclock, but an incredible simulation. :-) It
does not recognize resources addressed to xclock, because it is a
part of dash. It does recognize many resources, but unfortunately
at this time it doesn't recognize the normal xclock resources. This
should be remedied in the future.
> (The load menu option does, which is a win.)
That's because the load menu option actually runs xload itself. If
you'd rather, you can modify your clock menu option to start up
xclock instead of dash's internal analog clock, but it will cost
you memory.
> 3) It would be nice if the man page listed the command-line options (at
> least for the default setup).
I'm not sure what you mean. It does list the command-line options...
> 5) It would be really nice to be able to cut and paste text from the
> dashboard (or its idiot lights) with the mouse.
Future...
> 6) It would be nice if there were some more obvious way of telling
> whether selecting an item runs a program than whether it has an ellipsis
> after it.
This has been the subject of much discussion: how exactly _should_ this
user interface work? If you have any suggestions, please send them to
dash@athena.mit.edu, or post them directly to the adt discuss meeting
(adt being the former name of dash).
Craig Fields
Project Athena
