Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!sol.ctr.columbia.edu!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!pacbell.com!ucsd!sdcc6!beowulf!djohnson
From: djohnson@beowulf.ucsd.edu (Darin Johnson)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re: How to improve Workbench 2.0!
Message-ID: <16175@sdcc6.ucsd.edu>
Date: 30 Jan 91 18:46:54 GMT
References: <1991Jan27.105252.7019@marlin.jcu.edu.au> <7662@sugar.hackercorp.com>
Sender: news@sdcc6.ucsd.edu
Organization: CSE Dept., UC San Diego
Lines: 16
Nntp-Posting-Host: beowulf.ucsd.edu

In article <7662@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes:
>In article <1991Jan27.105252.7019@marlin.jcu.edu.au> glmwc@marlin.jcu.edu.au (Matt Crowd) writes:
>> 2) Quiting workbench.  Why should you be able to quit workbench
>> without running any programs?  You are left in a totally useless
>> position!
>
>How does Workbench know if you have programs running or not?

Hmmm, how about having a double click in an empty workbench window
raise a requester asking if Workbench or a CLI should be opened?
Easy enough to do with a custom input handler, but then if you forget
to run the handler...
-- 
Darin Johnson
djohnson@ucsd.edu
  - Political correctness is Turing undecidable.