frames and panes (East coast) versus overlapping independent windows (West coast)

• To: dmitchell@trc.amoco.com
• Subject: frames and panes (East coast) versus overlapping independent windows (West coast)
• From: Bill York <york%oakland-hills@lucid.com>
• Date: Thu, 17 Dec 92 15:57:22 PST
• Cc: clim@BBN.COM, bdavis@apctrc.trc.amoco.com
• In-Reply-To: "Donald H. Mitchell"'s message of Thu, 17 Dec 1992 09:20-0600 <19921217152053.2.DON@trc.amoco.com>
• Reply-To: York@lucid.com

   Date: Thu, 17 Dec 1992 09:20-0600
   From: "Donald H. Mitchell" <dmitchell@trc.amoco.com>
   Reply-To: dmitchell@trc.amoco.com

   With all those MacHeads and UnixGoons out there using CLIM, you'd
   think that if it were easy to make CLIM handle West Coast windows
   there'd be contributions in Cambridge and discussions in the CLIM
   list.  But, alas, I see none (although I vaguely remember but
   cannot find a short discussion on this).  I assume that the lack
   of discussion is not because West Coast windows are obvious
   (and thereby left up to the reader).  But, is it so?

There have already been good answers to this.  I just wanted to add
that several CLIM applications (specifically ones started in the MCL
environment, not surprisingly) use the "messy desktop" windowing
model.  About the only trick you have to learn is to make sure that
all the windows share the same io-buffer object so that an ACCEPT call
on one will allow input on any of them.  So, just use the
:INPUT-BUFFER init arg to your various OPEN-WINDOW-STREAM calls and
you can play with independent windows to your heart's content.


0,,

• frames and panes (East coast) versus overlapping independent windows (West coast)
• From: "Donald H. Mitchell" <dmitchell@trc.amoco.com>

• Prev: re: draft for Garnet FAQ
• Next: bug in clim:draw-ellipse?
• Index: CLIM Mailing list (1-Sep-92 to 31-Dec-92)
• Thread: CLIM Mailing list Index (1-Sep-92 to 31-Dec-92)