Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!husc6!husc7!hadeishi
From: hadeishi@husc7.HARVARD.EDU (Mitsuharu Hadeishi)
Newsgroups: comp.sys.amiga,comp.sys.mac,comp.sys.atari.st
Subject: Re: Better Windows?
Message-ID: <1976@husc6.UUCP>
Date: Wed, 13-May-87 14:05:59 EDT
Article-I.D.: husc6.1976
Posted: Wed May 13 14:05:59 1987
Date-Received: Sat, 16-May-87 04:09:51 EDT
References: <565@bloom-beacon.MIT.EDU> <1987May12.233757.24441@gpu.utcs.toronto.edu>
Sender: news@husc6.UUCP
Reply-To: hadeishi@husc7.UUCP (Mitsuharu Hadeishi)
Organization: Harvard Univ. Science Center
Lines: 24
Summary: Windows have their own menu systems on the Amiga
Xref: mnetor comp.sys.amiga:4778 comp.sys.mac:3107 comp.sys.atari.st:3421

pete@gpu.utcs.UUCP (Peter Santangeli) writes:
> On the subject of Window recursion, the one part of most windowing systems
>I find counter -intuitive is the difference between the desktop and a window.
> Wouldn't it make more sence to allow WINDOWS to have there own menu systems?
>These could be modal (only the active windows menus available) or semi-modal
>(active and desktop available). This kind of scheme would make multitasking
>much more intuitive.
> Now if someone could come up with a graphic rendition of Pipes and
>I/O routing, we'd be laughing...
>
>Pete

	The Amiga, in fact, does use this design.  The menus available
at the top of the screen are always the menus for the active window,
no other.  If you are running an application on the standard desktop,
you can get to the desktop menu bar by simply clicking in the background
area (i.e., outside of any window on the desktop), and then the desktop
menu is used.  Otherwise, the menu bar contains the menu for whichever
window is active.  I believe this is the design used in Servant, and
possibly the design used in Juggler (although I wouldn't know).  Clearly
this is necessary in a multitasking windowing scheme; for a single-tasking
machine, it is of much less importance.

				-Mitsu