Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!jade!lapis.berkeley.edu!oster
From: oster@lapis.berkeley.edu (David Phillip Oster)
Newsgroups: comp.sys.mac
Subject: Re: What happened to the 'universal window manager interface'?
Message-ID: <3086@jade.BERKELEY.EDU>
Date: Wed, 8-Apr-87 15:52:51 EST
Article-I.D.: jade.3086
Posted: Wed Apr  8 15:52:51 1987
Date-Received: Mon, 13-Apr-87 05:37:00 EST
References: <7331@boring.mcvax.cwi.nl> <458@laurel.wiley.UUCP>
Sender: usenet@jade.BERKELEY.EDU
Reply-To: oster@lapis.berkeley.edu (David Phillip Oster)
Organization: University of California, Berkeley
Lines: 19
Keywords: X windows

I haven't given it a really detailed look, but it seems reasonable to
write a library for your favorite Mac C compiler to take a program that
thinks its running under X and compile it to run under Quickdraw.

The philosophy of X is remarkably similar to QuickDraw, in parrticular
event handling, and the fact that X requires that applications be able to
redraw their windows.

Even if there are problems I haven't seen, it would still be possible to
emulate a subset of X under Quickdraw.  (Since the goal would be running
an X application on the Mac, the emulation library would probably have to
perform some of the functions usually done by an X window manager
application.)

The biggest problem is a user interface one: X itself seems to require
multiple mouse buttons although, since it is going from 3 to 5 mouse
buttons (with shift, command, and option modifiers: forget the keyboard,
just chord your ascii in!) applications are going to have to become more
tolerant of non-3-button mice.