Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!elroy!mahendo!jplgodo!wlbr!scgvaxd!trwrb!trwspp!spp2!sol!urban
From: urban@sol.SPS.TRW.COM (Michael Urban)
Newsgroups: comp.sys.mac
Subject: Re: X-windows for the Mac? (question)
Message-ID: <277@algol.sol.SPS.TRW.COM>
Date: Wed, 4-Nov-87 11:03:10 EST
Article-I.D.: algol.277
Posted: Wed Nov  4 11:03:10 1987
Date-Received: Sat, 7-Nov-87 16:50:11 EST
References: <16518@gatech.edu> <3083@husc6.UUCP> <383ec1cf.b0a1@apollo.uucp>
Reply-To: urban@algol.UUCP (Michael Urban)
Organization: TRW Inc., Redondo Beach, CA
Lines: 28

In article <383ec1cf.b0a1@apollo.uucp> nazgul@apollo.UUCP (Kee Hinckley) writes:
(in regards to porting the X Window System to the Mac)
>
>There is at least one non A/UX port too as well, I think someone at MIT
>was doing it.  However I doubt that you will see any port that will work
>over a modem.  Even at 9600 baud I doubt the throughput would be terribly
>good.

It would seem to me that another approach would be productive from the
point of view of writing portable applications: don't port the X
protocol, just implement the X library in a way that only allows
windows to be created on the local display, doing its window
creation and painting via the Mac toolbox.  With this approach, you
could run things like xterm, xmille, etc., as long as you don't try
to talk to a remote server or client, and you could build/prototype
(X-based) window applications that run on your Mac and can be
trivially ported to Suns, Vaxen, etc.  Obviously, this leaves out an
important aspect of X, but the result would still, I think, be valuable.

Or am I missing some important issue?



-- 
   Mike Urban
	...!trwrb!trwspp!spp2!urban 

"You're in a maze of twisty UUCP connections, all alike"