Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!zodiac!jdye
From: jdye@zodiac.ADS.COM (John W. Dye Jr.)
Newsgroups: comp.lang.lisp
Subject: Re: Unix Lisp Environments (why the slow evolution)
Message-ID: <7820@zodiac.UUCP>
Date: 6 May 89 19:37:02 GMT
References: <7802@zodiac.UUCP> <40215@think.UUCP>
Sender: news@zodiac.UUCP
Reply-To: jdye@ads.com (John W. Dye Jr.)
Organization: Advanced Decision Systems
Lines: 32

In article <40215@think.UUCP> barmar@kulla.think.com.UUCP (Barry Margolin) writes:
>In article <7802@zodiac.UUCP> jdye@ads.com (John W. Dye Jr.) writes:
>>2)  The window systems keep changing.  First there was sunview. Then there
>>    were X and NeWS.  Now there is (soon) a NeWS/X merge (with suntools
>>    support also).  Developers of lisp programming environments have had
>>    to program on a moving target (the window systems).  Unfortunately,
>>    most of the neat stuff that lisp programming environments do are
>>    window based (window-debuggers, fancy editors). 
>
>The solution to this is coming soon.  International Lisp Associates
 ************

A solution to this is coming from ILA.  Another from Sun, Another from
Franz inc.  Lucid, of course, has their own solution (independent of Sun's
solution).  Then there is Coral Common Lisp etc...  

I dont know which vendors belong to ILA.  Obviously symbolics does.
Does Sun? Lucid? Franz?

Im pretty sure Sun and Franz wouldn't be happy with a re-implementation
of Slimebolix windows.  Will that window system be CLOS based? 

>Barry Margolin
>Thinking Machines Corp.

The problem here is a recursive version of the window-systems problem.
Now, instead of having to write environments that target a specific
window system, we will be writing environments that target specific
window-system-independent LISP window systems.   Deja Vu.

JD
jdye@ads.com