Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!usc!snorkelwacker!think!kulla!barmar
From: barmar@kulla (Barry Margolin)
Newsgroups: comp.lang.lisp
Subject: Re: Developing over CLX
Message-ID: <31073@news.Think.COM>
Date: 26 Oct 89 02:33:35 GMT
References: <1989Oct24.183645.9930@wucs1.wustl.edu> <31035@news.Think.COM> <1989Oct25.155852.20583@wucs1.wustl.edu>
Sender: news@Think.COM
Distribution: na
Organization: Thinking Machines Corporation, Cambridge MA, USA
Lines: 21

In article <1989Oct25.155852.20583@wucs1.wustl.edu> sbc@wucs1.UUCP (Steve B Cousins) writes:
>I read your reply as saying that I probably don't want to use CLX alone to
>do anything with.  I was hoping to be able to sit at my Mac and run Mac X
>connected across the net to a Sun running Franz's product as an alternative
>to using Allegro on the Mac when I needed more performance.  I can do that
>with Telnet now, but I was hoping for a better development environment.
>Is it safe to say that such things are still pretty premature?

Yes, you managed to figure out the answer.  Developing over CLX is like
developing on Unix over Xlib -- they're just low-level subroutine
libraries.

If you have Mac X and a Sun, what you CAN do is run GNU Emacs on the Sun,
having it display on the Mac using X.  You can then run Franz in a
shell-mode buffer inside Emacs.  If you're developing CLX-based
applications, they can then display on the Mac as well.

Barry Margolin, Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar