That's an X window opened by OpenMCL using my hack-and-slash port of CLX (running XDarwin and the OroborOSX window manager on my PowerBook).
It's kind of funny. There's no reason that CLX couldn't have been ported to work with MCL on a Mac at any point in the last 10 years, really, though not too many people were running an X server on a Mac, and the number of people running lisp applications on a Mac but wanting to put the display on a remote X machine was probably pretty low. Now, of course, you've got OpenMCL, which has no real GUI support yet, and XDarwin, and suddenly CLX starts to look useful.
I chose the CLOCC version of CLX (it's kind of unfortunate that there are so many versions) because it claimed to be moving the code toward ANSI, even though I dislike the CLOCC PORT package that it uses for sockets and multiprocessing support.
It will take a bit more work before this is ready for real use, but not too much.
Posted by jjwiseman at July 10, 2002 02:05 AMThe use of the PORT package by the CLOCC version of CLX is only a temporary solution. Peter Van Eynde, the CLX/CLOCC maintainer, said that he will eventually remove the dependency on PORT.
Have (de)fun,
Paolo
Cool. A canonical cleaned-up CLX that was structured to be as easy as possible to get running in different lisps (as easy as McClim, say) would be a nice thing for Lisp in general.
Using CLOCC with it can come later, if desired. (Does it really need to be using split-sequence?)
Posted by: jjwiseman on July 11, 2002 06:48 PMI usually use Exodus on my Mac as a X11 server. There is also a MacOS X version of it. I also successufully used CLX in MCL years ago. Stuff like CLUE/CLIO can be easily used in MCL with CLX.
Rainer
Posted by: Rainer Joswig on July 12, 2002 12:27 AMI tried getting McClim to run, actually, but ran into problems with MCL's non-AMOP mop. In particular, the lack of ensure-class.
Posted by: jjwiseman on July 14, 2002 07:53 PM