[developers] Lkb topmenu
Ann Copestake
aac10 at cl.cam.ac.uk
Sun Jan 3 18:25:41 CET 2016
Hi,
I'm afraid I gave up on getting a version working with McCLIM, and I
suspect nobody else has tried, though I hope anyone who has will chip in
with experiences. I see that you have already emailed the McCLIM list.
It looks like there's a different interpretation of desired behaviour
between Allegro CLIM and McCLIM (it isn't too surprising that happens in
some places), so I guess you'd have to make this a place where the code
is different for the two different CLIMs. As far as I'm concerned,
we're trying to keep the CLIM code running under Allegro, but not
developing it further. I'd note that a lot of the functionality of the
original CLIM interface is available with the LUI, which is now the
prefered interface for most people, though I'm not sure whether there's
a substitute for the bits you're working on right now.
http://moin.delph-in.net/LkbLui
All best,
Ann
On 03/01/2016 14:56, John R. Towler wrote:
> Hello,
>
> I am working on getting an open source compile and build for the
> Lkb. I have a compile on sbcl with experimental threads. I am
> running into an error of (:command-table something) needing a
> list as argument. I have McCLIM and it runs. It containes an
> example LispListener which runs and has code like the above
> (:command-table unquoted-something). This is the current
> obstacle. Clisp compiles also with McCLIM and the Allegro
> compat functions from portableaserve. Execution dies for clisp
> on lacking threading. This is experimental in clisp. I would
> appreciate any help, it appears that but for the CLIM macro,
> define-application-frame's argument (:command-table
> lkb-top-command-table) not being a list, this code would run.
>
> NetBSD-6.1.4, sbcl-1.3.1-plus, cliki.net and common-lisp.net
> open source tools, McCLIM which works for its example code.
>
>
> Sincerely,
> John R. Towler
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.delph-in.net/archives/developers/attachments/20160103/20dabce1/attachment.html>
More information about the developers
mailing list