Path: utzoo!utgpu!watmath!clyde!att!oucsace!oucs!arp From: arp@pdp.cs.OHIOU.EDU (John Gordos) Newsgroups: comp.sys.amiga Subject: WorkBench Dreams Keywords: I wish.. Message-ID: <720@pdp.cs.OHIOU.EDU> Date: 8 Dec 88 15:20:33 GMT Organization: Ohio University CS Dept., Athens Lines: 42 Folks, I've got something that I'd REALLY like to see added to the WorkBench; Being able to "click" on an icon AND while it opens, "click" on another icon AND... well, you get the idea. It would be nice to click on a drawer, have the window open, see the next drawer you want (but not all the icons in the first have appeared yet) and click on "drawer number 2" and have it start to open. That sort of thing. Another buy would be to be able to click on the close gadget of a window and have it close BEFORE it displays all the icons in the window. I'm sure that the problem probably lies in layers and that it'd be non-trivial to implement, but it'd really get the point of multi-tasking across. My wife doesn't understand multitasking really; All she knows is that the WorkBench is enough like a MAC that she can use it. If the WorkBench seemed to multitask more than it does, it would surely help us both; I can scoot around with that mouse much quicker than my floppies can display a drawer! And, IMHO, the shell's use of run and aliases is busted; If you are running a shell and use run to "spawn" a new process, it should spawn a shell, and not a cli. It's important to present a consistent interface to an end user. I *know* why an alias isn't expanded in a run command, but I also think that there isn't much point in aliasing something if it won't be used 100% consistently. Needing to remember that aliasing works in all cases EXCEPT with run is not consistent. Waiting for flames, John -- ============================================================================= John A. Gordos, III oucs!crta!gordos SAMI/Burke Distributed Systems Technical Support Cincinnati, Ohio "Go Bengals!!"