Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!think!ames!sdcsvax!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: Let's use screens!
Message-ID: <8708250458.AA18654@cory.Berkeley.EDU>
Date: Tue, 25-Aug-87 00:58:00 EDT
Article-I.D.: cory.8708250458.AA18654
Posted: Tue Aug 25 00:58:00 1987
Date-Received: Wed, 26-Aug-87 02:08:42 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 21


>It sure would be nice to move applications from screen to
>screen.  This way, one screen could be for host communication
>(a window for downloading, a window for Tek graphics, and a
>window for the terminal emulation.)  Another screen could be
>used for TeX development (an editor, the previewer, and TeX,

	This is partially solved with MWB.  MWB is CLI based, and allows
you to cause windows spec'd to open on the workbench screen to open somewhere
else.  It automatically routes OpenWindow() calls for the workbench screen
to the current 'MWB' screen.  It does *NOT*, however, allow you to move
windows from screen to screen, nor open windows on other program's custom
screens, nor force programs which open windows in their own custom screens
to open them in an alternate screen instead.  You can specify everything
about the one or more 'MWB' screens except the colormap (an oversite... use
that other PD program that allows you to set palette colors of arbitrary 
screens).

	(I sent Tom a copy).  

					-Matt