Xl1200 as x server

[miller@GEM.cam.nist.gov (Bruce R. Miller)]

    Date: Thu, 2 Aug 90 17:35 EDT
    From: Barry Margolin <barmar@Think.COM>

	Date: Thu, 2 Aug 90 14:23 EDT
	From: miller@GEM.cam.nist.gov (Bruce R. Miller)

	Just how does  this work  (for the  X naive)?

    It's all done through the magic of object-oriented programming.  ...
						    barmar
Well, I didn't mean That naive ! :>  (but thanks anyway)
What I had in mind was the following:

Not knowing the X protocol, it  is not inherently obvious that  the full
protocol used by  TV and  DW CAN  be (practically)  translated into  the
appropriate X.  That is to say, although equivalent functionality  could
most likely be achieved in X at some level in the application, the TV/DW
protocol has been decomposed into certain operations, some of which  may
have no equivalents.   Take some random old TV-style application and  it
is throwing all  sorts of  random messages,  high-level and  low, at the
window-stream.  (I  mean,  can  you  honestly  say that TV:windows HAD a
protocol? You  and  I  both  have  spent  LOTS of time figuring out what
messages were sent and who handled which parts in which order, before we
were `saved' by  DW! "Lets  see, If  I put  my-mixin right  here between
tv:window-with-foo-usurped-but-no-scrolling                          and
tv:stream-input-from-kludged-borders-mixin, and  define  a  whopper  for
:update-vsp-for-changed-borders (hmm, what's the argument list), it  just
might work") For it to work in X, ALL those messages have to be  handled
by the X stream.

On the basis of other replies, though, it seems that most things DO work.
I just dont want to fork over the bucks, install it, and have Macsyma come
up saying

Command: Macsyma
You cannot do plotting in this context.You cannot do plotting in this context.You cannot do plotting in this context.
This is Macsyma 416.15 for Symbolics 3640 Series Computers.

(alright, already, I wont try!!!)

bruce