March 2005 - mcclim-devel - mailman3.common-lisp.net

[mcclim-devel] Drawing graphs & scaling
by Thibault Langlois 22 Apr '05

22 Apr '05

Hello, I would like to be able to scale a graph: (defmethod plot ((object tree) stream) (with-scaling (stream 0.7) (draw-graph (list (root-node object)) #'draw-node-colors :stream stream))) where draw-graph is directly inspired from an example in allegro CLIM manual: (defun draw-graph (root-nodes draw-node-function &rest keys) (apply #'format-graph-from-roots root-nodes #'(lambda (node s) (multiple-value-bind () (with-output-as-presentation (s node 'node) (funcall draw-node-function node s)))) #'(lambda (n) (if (visible-p n) (children n))) keys)) and draw-node-colors draws a node using draw-rectangle*. The problem is that when the scaling factor is not 1 the nodes are not correctly placed (although they are correctly scaled) with respect to arcs. Any ideas ? Thanks. Thibault

3 6

[mcclim-devel] Better defaults for CLX backend
by Christophe Rhodes 02 Apr '05

02 Apr '05

Hi, Attached are a diff and a new file to implement better defaults for the clx server path: parsing $DISPLAY as a Unix user might expect. Behaviour should be unchanged in the case that the $DISPLAY environment variable is unreadable. The immediate effect of this patch is that clim over ssh will work. That said, I have completely failed to test this patch even to the point of compiling it, as locally both my sbcl and my clx are broken. If someone could test this and report back (or commit it themselves), that would be good. Cheers, Christophe

1 1

[mcclim-devel] sb-bsd-sockets
by Boris Tschirschwitz 31 Mar '05

31 Mar '05

Hi. I am trying to use McCLIM with openmcl. When compiling the beagle backend I get the error message that sb-bsd-sockets can't be found, apparently clx depends on it and mcclim depends on clx, even with beagle. Making sb-bsd-sockets from sbcl-contrib known to asdf helps until sb-bsd-sockets wants sb-grovel and eventually sb-ext. This one I can't find on sbcl. Am I really supposed to use all these SBCL packages? If so, where do I get the sb-ext? Thanks, Boris.

5 4

[mcclim-devel] Image drawing
by Milan Zamazal 30 Mar '05

30 Mar '05

Since image drawing (in clim-extensions.lisp) was excluded in McCLIM 0.9.1, I've implemented my (very primitive for now) own code for that in Springtail (http://www.zamazal.org/software/springtail/index.html) This is just to let you know that if anybody wanted to add image drawing support to McCLIM again, I'd like to cooperate. Regards, Milan Zamazal -- _/_\_/_ o _\_/_\_ o _/_\_/_ o _\_/_\_ o BEWARE! -<_|_|_|_><-- -<_|_|_|_><-- -<_|_|_|_><-- -<_|_|_|_><-- *Bugs* are / \ / o \ / \ o / \ / o \ / \ o approaching!

1 0

[mcclim-devel] Sample code
by David Christiansen 27 Mar '05

27 Mar '05

I've written a Connect Four game that uses McCLIM, complete with a computer player, and I think that it might be a nice little inclusion into the sample code section of McCLIM (i.e., the clim-demos package). How can I go about submitting it? ;;--------------------------------------------------------------- ;; -David Christiansen ;;

1 0

[mcclim-devel] Flipping sheet coords
by Duncan Rose 25 Mar '05

25 Mar '05

This is probably rather Cocoa-centric, so I'll probably be boring anybody that doesn't know any of Apple's frameworks with the following... I've been looking at the Beagle back end again recently looking to complete the remaining functionality and speed it up somewhat. One of the things I want to do to hopefully speed things up is move to a delayed drawing implementation (which is the way Apple recommend doing things anyway; all drawing is done in a 'drawRect' method which is invoked as part of the main event loop by the underlying windowing system). In order to make this work I've migrated the text drawing to append glyphs to an NSBezierPath subclass; in order to implement the delayed drawing I just stack all bezier path objects up in an array and stroke or fill them at the appropriate time. The problem I have is that Cocoa and McCLIM have different coordinate systems (the y-axes are reversed) by 'default'. Previously I dealt with this by setting the view up to be 'flipped' which is standard Cocoa functionality. This works in general but text is rendered upside down. What I'd *like* to do is to be able to set a transform which would automatically take care of this within McCLIM (rather than within Cocoa). What I'm hoping is that there's an easy solution to this (such as applying an inverting transform the the graft and having this by default apply to anything grafted onto it). So my question boils down to "does using a :graphics oriented graft rather than a :default orientation make any difference at all to anything attached to that graft"? An additional question might be "if not, should it?" (I'd like to have a CLIM solution to this but if there appears not to be one I'll hack something into the back end to do it via Cocoa - it seems to me that if I apply the appropriate transform to the graft things should 'just work' but maybe I'm misunderstanding how things fit together). Also, who do I need to see to get CVS commit privs again or should I just be submitting patches? Thanks, -Duncan

1 0

[mcclim-devel] Freetype bindings
by Christophe Rhodes 23 Mar '05

23 Mar '05

Hi, I've been playing with the bindings to freetype in Experimental/freetype, with a view to using them in one of my apps -- there is a font which I need to use which is available to me in truetype format (and, in addition, it makes the Climacs window look pretty). I've run into multiple problems, most of which I've worked around in some way or other. One which is definitely not this list's problem is the fact that sbcl miscompiles freetype-ffi.lisp; it gets confused over some forward declarations, and subsequently refuses to do anything with certain foreign structures. I believe the sbcl experts are working on this problem; however, there is a simple workaround, which is to load the freetype-ffi.lisp file as source. A more serious problem lies in the fact that the ffi bindings are very definitely 32-bit centric; certain things are defined as (signed 32) or (unsigned 32) when they should be long or unsigned-long. (This causes segmentation faults on 64-bit platforms). I have manually corrected the bindings, but I think the right answer is to generate the bindings themselves as part of the compilation process: in other words, do something similar to sbcl's sb-grovel, and ask the C compiler on the host system to emit suitable Lisp code, using sizeof, offsetof, and the C preprocessor itself. One word of warning at this point: it is easy to crash your lisp if you're not careful, because the bindings are not fully type-declared, so sbcl spews compiler diagnostics to *standard-output* when calling the freetype functions. This is bad if the freetype functions are being called in order to emit characters to a clim pane bound to *standard-output*... I've been using (handler-bind ((compiler-note #'muffle-warning)) (climacs-gui::climacs)) or similar to work around this. The remaining glitch -- one that I have not managed to solve, is that there are visual artifacts with the bindings. A full redraw usually solves any such artifacts, but during the course of interaction, characters are often misplaced. A chance mention on IRC suggests that this might be caused by insufficient display-finish-outputs; does anyone have any suggestions as to where to look for these? A screenshot, for the interested: <http://www-jcsu.jesus.cam.ac.uk/~csr21/tabcode-font.png>. Cheers, Christophe

1 0

[mcclim-devel] Copying text to clipboard loops displaying messages to Konsole
by Paolo Amoroso 22 Mar '05

22 Mar '05

When I copy some text with Shift-left-click from the CLIM Listener for later copying somewhere else, I get an infinite loop that displays messages (all identical) like this to the KDE Konsole from which I have started the Listener: #<CLIM-CLX::CLX-SELECTION-REQUEST-EVENT {5850A54D}> is an instance of type CLX-SELECTION-REQUEST-EVENT it has the following slots: TIMESTAMP: 5010524 SHEET: #<CLIM:INTERACTOR-PANE CLIM-LISTENER::INTERACTOR {58B8A0CD}> REGION: <unbound> SELECTION: :PRIMARY REQUESTOR: #<XLIB:WINDOW :0 31457298> TARGET: :COMPOUND_TEXT PROPERTY: :_QT_SELECTION If I later paste with Shift-middle-click the clipboard selection to another Konsole pane, I get a garbled string similar to that described here: http://common-lisp.net/pipermail/mcclim-devel/2004-December/002731.html I have to quit the Listener in order to stop the infinite loop. I use CMUCL Snapshot 2005-02 with the latest McCLIM CVS sources under Slackware Linux 10.0, with a 2.6.10 kernel. Paolo -- Lisp Propulsion Laboratory log - http://www.paoloamoroso.it/log

4 16

[mcclim-devel] Gadgets in accepting-values (again)
by Anthony Juckel 22 Mar '05

22 Mar '05

With the latest McCLIM CVS, displaying a gadget within accepting-values seems to work quite well now. Unfortunately, I feel that I'm doing something wrong with the functionality. At first, I tried to simply call throw-object-ptype from my gadget's value-changed-callback (it inherits from value-gadget), but that seemed to have no effect. The function was called, but I'm unsure how that thrown value was supposed to propogate. Who is supposed to "catch" it? I finally settled on the following to get my value properly propogated: :value-changed-callback #'(lambda (gadget value) (declare (ignore gadget)) (let ((query (find query-identifier (climi::queries climi::*accepting-values-stream*) :key #'climi::query-identifier :test #'equal))) (setf (climi::value query) value) (setf (climi::changedp query) t)) (climi::throw-object-ptype value `(trait-rating ,max)) (debug-msg "Gadget value changed to: ~A" value)) The throw-object-ptype at near the bottom of the callback remains, but doesn't appear to do anything. This method strikes me as quite unclean for a few reasons, not the least of which is relying on a few unexported symbols from clim-internals. One other thing: com-select-query is not called during the operation of my gadget. Looking at the behavior of the popup menu, I see that it is displayed as a simple value until the query is selected, at which point select-query blocks waiting for the user to make a choice from the newly-drawn popup menu. I'm not sure how to do functionality similar to that in my case. The user may at any time click my gadget to change its value, and I am unsure how to tie in select-query for two reasons: 1) I still don't quite get presentation-to-command-translators, so I don't know how I can make any click on my gadget also translate into com-select-query, as well as having the click register with my gadget to properly change its value. 2) Even if I get com-select-query to be called, I'm unsure how I would block within select-query until the user selects a value in the query. Could anyone help me shed some light on these issues? Anthony W. Juckel

1 0

[mcclim-devel] Possible bug
by David Christiansen 21 Mar '05

21 Mar '05

Hello all, I'm new to the list. I've been writing a little Connect 4 clone with McClim and I think I found a place where the implementation diverges from the standard. I'm using the Mothering Sunday release. When I try to (make-pane 'option-pane :value "foo" :mode :exclusive :items '("foo" "bar")), I get an error saying that :exclusive is not a member of type (or :some-of :one-of). It looks to me as though the spec says that those options should be called :exclusive or :nonexclusive, though :one-of and :some-of seem to work just fine to me. The relevant section of the spec (chapter 30) can be seen at: http://www.mikemac.com/mikemac/clim/gadgets.html Am I reading it correctly? If so, I'll try to grab a recent CVS and work up a patch later this week (though, being a newbie, I'd want someone to see it). It seems localized enough that I should be able to figure it out. Thank you all for this handy library! ;;------------------------------------------------------------------ ;; -David Christiansen ;;

2 3

[mcclim-devel] Adding vertical orientation to Listener's graphing commands
by Paolo Amoroso 16 Mar '05

16 Mar '05

The very simple patch described in this blog entry: McCLIM grapher now supports vertical orientation http://www.paoloamoroso.it/log/050316.html adds vertical orientation to some of the CLIM Listener's class graphing commands. It is easy to extend the functionality to other similar commands. Paolo -- Lisp Propulsion Laboratory log - http://www.paoloamoroso.it/log

1 0

[mcclim-devel] Please remove the debian/ directory
by Milan Zamazal 12 Mar '05

12 Mar '05

Please remove the obsolete debian/ directory from CVS. The package is contained and maintained in Debian. Thanks, Milan Zamazal -- real programmer? don't get me started. if you need to hide your pathetic excuse for a carreer behind super-macho languages like C, C++, and/or Perl instead of writing clean, maintainable, efficient code, you aren't much of a real programmer in my view. -- Erik Naggum in comp.emacs

1 0

[mcclim-devel] Another Beagle %set-port-keyboard-focus 'patch'
by Duncan Rose 11 Mar '05

11 Mar '05

Hrm. Not sure how to turn this into a patch without some messing around (will cvs diff generate a patchfile with the right options?) but since it's only one line... I think this was overlooked in the recent patches (or maybe I'm not loading Beagle in the preferred manner any more) -Duncan Index: beagle-backend.asd =================================================================== RCS file: /project/mcclim/cvsroot/mcclim/Backends/beagle/beagle-backend.asd,v retrieving revision 1.1 diff -r1.1 beagle-backend.asd 27c27 < #:set-port-keyboard-focus --- > #:%set-port-keyboard-focus

2 1

[mcclim-devel] Proper place for inspector documentation
by Peter Scott 10 Mar '05

10 Mar '05

I wrote some documentation on how to extend the inspector, and it's in TeX format, but I'm not sure where to put it. Should it go in Doc/manual.tex? If so, how? Should I introduce a Part 3 for utility programs like the listener and the inspector? Or should it go in its own seperate manual? -Peter

2 1

[mcclim-devel] Scigraph
by Fred Gilham 10 Mar '05

10 Mar '05

Hi, Here's a scigraph.asd file to allow easy building of Scigraph. It seems like it almost (where almost = about 95%) works. Great work by everyone. Put this file in mcclim/Apps/Scigraph and do the usual: (asdf:oos 'asdf:load-op :scigraph-system) ;;; -*- Mode: Lisp; Syntax: Common-lisp; Package: Common-Lisp-User -*- (in-package :common-lisp-user) (asdf:defsystem scigraph-system :serial t :components ((:module "dwim" :serial t :components ((:file "package") (:file "feature-case") (:file "macros") (:file "tv") (:file "draw") (:file "present") (:file "extensions") (:file "wholine") (:file "export"))) (:module "scigraph" :serial t :components ((:file "package") (:file "copy") (:file "dump") (:file "duplicate") (:file "random") (:file "menu-tools") (:file "basic-classes") (:file "draw") (:file "mouse") (:file "color" ) (:file "basic-graph") (:file "graph-mixins") (:file "axis") (:file "moving-object") (:file "symbol" ) (:file "graph-data") (:file "legend" ) (:file "graph-classes") (:file "present" ) (:file "annotations") (:file "annotated-graph") (:file "contour" ) (:file "equation") (:file "popup-accept") (:file "popup-accept-methods") (:file "duplicate-methods" ) (:file "frame" ) (:file "export" ) (:file "demo-frame"))))) -- Fred Gilham gilham(a)csl.sri.com REPRODUCTIVE RIGHTS: the right not to reproduce, no matter what else you do. PLANNED PARENTHOOD: an organization that helps you plan to avoid becoming a parent.

1 0

[mcclim-devel] problem building McCLIM mothering on Linux ACL 6.2
by rpgoldman＠real-time.com 08 Mar '05

08 Mar '05

I, too, was unable to do any testing before the release. I just updated my repository, wiped out the fasls, and tried to rebuild (this time from the asdf def, instead of system.lisp). I got a problem with package dependencies. Building mcclim/Looks/pixie.lisp got an error because the IMAGE package was undefined. Here's the error message. I'll have a look to try to track down the bug whenever I can get any time. Error: Package "IMAGE" not found. [file position = 36821] [condition type: READER-ERROR] Restart actions (select using :continue): 0: retry the compilation of /home/rpg/lisp/mcclim/Looks/pixie.lisp 1: continue compiling /home/rpg/lisp/mcclim/Looks/pixie.lisp but generate no output file 2: Retry performing #<ASDF:COMPILE-OP NIL @ #x71446b3a> on #<ASDF:CL-SOURCE-FILE "Looks/pixie" @ #x714382aa>. 3: Continue, treating #<ASDF:COMPILE-OP NIL @ #x71446b3a> on #<ASDF:CL-SOURCE-FILE "Looks/pixie" @ #x714382aa> as having been successful. 4: Return to Top Level (an "abort" restart). 5: Abort entirely from this process. Best, R

2 3

[mcclim-devel] more beagle stuff
by Cyrus Harmon 08 Mar '05

08 Mar '05

While I'm at it, the following made the command/esc/etc... key situation much better for climacs:

1 0

[mcclim-devel] Announcing McCLIM 0.9.1 - "Mothering Sunday"
by McCLIM developers 08 Mar '05

08 Mar '05

The McCLIM developers are happy to release version 0.9.1 of McCLIM. It was extensively tested on SBCL (threaded and unthreaded), OpenMCL and CMUCL. It's also known to work with Allegro Common Lisp (tested with 6.2 Trial Edition). Lots of things changed since the last release, so I appended the release notes after the announcement. We're hoping to make this release the first in a series of time-boxed releases of McCLIM. You can get a tarball at <http://common-lisp.net/project/mcclim/downloads/mcclim-0.9.1.tar.gz>. Of course, we are looking forward to comments and bug reports. Please direct these at mcclim-devel <at> common-lisp.net. The current list of known bugs can be found at <http://mcclim.cliki.net/Bug>. Have fun using McCLIM (and build good things with it), the McCLIM developers. RELEASE NOTES FOR McCLIM 0.9.1 - "Mothering Sunday": Changes to the McCLIM Installation Process ========================================== McCLIM now comes with a native ASDF system definition in mcclim.asd, along with the traditional (still ASDF-compatible) system.lisp. See INSTALL.ASDF for details. Changes to Backends =================== Support for Copy&Paste of selections (both into and out from McCLIM applications) in the X11 backend was added. Copying text from McCLIM into some applications (and vice versa) like KDE's Konsole is broken, unfortunately. Shift + left-mouse-drag and Shift + mouse-middle-down now activate a selection and paste in your McCLIM application, respectively. There is now rudimentary support for printing non-Latin1 characters to X11 ports on SBCL. Beagle, A new experimental backend using Mac OS X's Cocoa bindings was added. Note that this backend is still incomplete and breaks in some places. It is not loaded automatically. To try it out, consult Backends/beagle/README. Changes to the Manual ===================== A chapter on presentation types was added. The chapter on command tables was improved. Changes to Contributed Applications and Examples ================================================ Clouseau, a graphical Inspector application was added. The CLIM Listener saw many improvements, among these: package graphing, better directory stack handling and a new Edit Definition command. A Method Browser was added to the examples. Status of the CLIM 2 Spec Implementation ======================================== Here is a list of what we think works, organized by chapters and sections of the CLIM 2 specification. Chapter 3 Regions Mostly finished. There are some troublesome parts of the specification that may not be implemented for all possible regions, for instance region-contains-region-p. There may not be an efficient way of implementing this function for all kinds of regions. Chapter 4, Bounding rectangles Finished Chapter 5, Affine transformations Finished Chapter 6, Overview of window facilities Finished Chapter 7, Properties of sheets Finished, though the correct behavior of sheet transformations may not have been tested. Chapter 8, Sheet protocols Finished Chapter 9, Ports, Grafts, and Mirrored sheets Finished Chapter 10, Sheet and medium output facilities Finished Chapter 11, Text styles Finished Chapter 12, Graphics Finished Chapter 13, Drawing in Color I am note sure about the state of this. I thought we were doing only full opacity and full transparency, but I see traces of more general designs. Chapter 14, General Designs The composition of designs is not supported. We do support regions as designs. Chapter 15, Extended Stream Output Extended output streams are fully supported. Chapter 16, Output Recording Output recording is mostly implemented. We do not have a true standard-tree-output-record type or the R-tree type of real CLIM, so some operations may be slow with lots of output records. make-design-from-output-record is not implemented. *Note*: the coordinates in output records are relative to the stream. This is in conformance with the Spec, but not necessarily compatible with other CLIM implementations. There is now a protocol in place for Drag-and-Drop of output records. Output recording inside formatting-tables now works. Chapter 17, Table Formatting Table formatting is completely implemented. Chapter 18, Graph Formatting Graph formatting is fully implemented. The :hash-table argument to format-graph-from-roots is ignored. Chapter 19, Bordered Output Bordered output is fully supported. The :move-cursor argument to surrounding-output-with-border is now working. Chapter 20, Text Formatting With the exception of the :after-line-break-initially argument to filling-output, this chapter is fully implemented. Chapter 21 Incremental Redisplay The updating-output interface to incremental redisplay is implemented. McCLIM makes no effort to move i.e., bitblit, output records; they are always erased and redrawn if their position changes. This is much more compatible with support for partial transparency. The :x, :y, :parent-x and :parent-y arguments to redisplay-output-record are ignored. McCLIM follows the spirit of 21.3 "Incremental Redisplay Protocol", but we have not tried very hard to implement the vague description in the Spec. augment-draw-set, note-output-record-child-changed and propagate-output-record-changes-p are not implemented. Incremental redisplay in McCLIM can suffer from performance problems because there are no spatially-organized compound output record types. The generic function incremental-redisplay is now implemented. Chapter 22, Extended Stream Input The implementation of extended input streams is quite complete. (setf* pointer-position) is not implemented. There is no stream numeric argument, so that slot of the accelerator-gesture condition is always 1. drag-output-record and dragging-output are now implemented. Chapter 23 Presentation Types Most of the literal specification of this chapter is implemented. Specific accept and present presentation methods for some types are not implemented, so the default method may be surprising. The output record bounding rectangle is always used or highlighting and pointer testing. presentation-default-processor is not implemented. The presentation method mechanism supports all method combinations. The body of a presentation method is surrounded with a block of the same name as the presentation method, not just the magic internal name. The method by which presentation type parameters and options are decoded for the method bodies is a bit different from real CLIM. In particular, you cannot refer to the type parameters and options in the lambda list of the method. The NIL value of presentation-single-box is now supported. Presentation type histories are now partially implemented. The gesture C-M-y should recall the last entered presentation. define-drag-and-drop-translator is now implemented. Chapter 24 Input Editing and Completion Facilities with-input-editor-typeout is not implemented. The noise strings produced by input-editor-format and the strings produced by presentation-replace-input are not read-only. This could lead to interesting "issues" if the user edits them. Only a few of the suggested editing commands are implemented. An additional command that is implemented is control-meta-B, which drops into the debugger. add-input-editor-command is not implemented. with-accept-help is not implemented. Chapter 25 Menu Facilities The protocol is implemented, but McCLIM doesn't use it to draw command table menus. Chapter 26 Dialog Facilities McCLIM contains a basic, somewhat buggy implementation of accepting-values. There is little user feedback as to what has been accepted in a dialog. The user has to press the "Exit" button to exit the dialog; there are no short cuts. There are no special accept-present-default methods for member or subset presentation types. Command-buttons are not implemented. There is no gadget-based implementation of accepting-values. own-window is not supported. The internal structure of accepting-values should be "culturally compatible" with real CLIM; if you have some spiffy hack, check the source. Chapter 27 Command Processing command-line-complete-input is not implemented (the functionality does exist in the accept method for command-name). display-command-table-menu and menu-choose-command-from-table are not implemented. Menu-command-parser is not implemented, though the functionality obviously is. Nothing is done about partial menu commands. There is no support for numeric arguments. The command-or-form presentation type is not implemented. Chapter 28 Application Frames raise-frame, bury-frame and notify-user are not implemented. :accept-values panes are not implemented. frame-maintain-presentation-histories, frame-drag-and-drop-feedback and frame-drag-and-drop-highlighting are not implemented. execute-frame-command ignores the possibility that frame and the current frame might be different. display-command-menu isn't implemented. command-enabled is now implemented. Chapter 29 Panes Due to the way the space-allocation protocol is implemented, it is not easy to create application-specific layout-panes. Client code needs to know about :AROUND methods to compose-space, but they are not mentioned in the spec. restraining-pane is partially implemented. Chapter 30 Gadgets This chapter is implemented.

2 1

[mcclim-devel] help needed with the beagle backend
by Tom Winchester 04 Mar '05

04 Mar '05

Hi there. I have been trying to get the beagle back-end for mcclim running. I am using use openmcl 0.14.2-p1, mac os x 10.3.8, and a fresh cvs of mcclim taken this morning. The clx back-end runs nicely -thanks to the splendid effort of the mcclim team. My first attempt consisted of executing the statement (asdf:operate 'asdf:load-op 'beagle). Even when repeated in an OpenMCL Listener, the result was: > Error in process Listener(3): Cannot IMPORT "SET-PORT-KEYBOARD-FOCUS" from package "CLIMI" > While executing: CCL::OPERATION-ON-ALL-SPECS > Type :GO to continue, :POP to abort. > If continued: Ignore attempt to IMPORT "SET-PORT-KEYBOARD-FOCUS" from package "CLIMI" Type :? for other options. 1 > I then examined the documentation in the Backends/beagle directiory of the mcclim (cvs) distribution. The load files essentially perform the following steps inside the OpenMCL Listener window: (load "/opt/local/share/openmcl/0.14.2-p1/tools/asdf") (pushnew "/Users/tom/.asdf-install-openmcl-dir/systems/" asdf:*central-registry*) (asdf:operate 'asdf:load-op :asdf-install) (asdf:operate 'asdf:load-op 'clx) (asdf:operate 'asdf:load-op :mcclim) (asdf:operate 'asdf:load-op :clim-examples) (asdf:operate 'asdf:load-op :clim-listener) (asdf:operate 'asdf:load-op :beagle) This is equivalent to my current ~/.openmclrc file, except that all of this is stated to be done inside the OpenMCL Listener, and the final statement. Upon pasting the above sequence of statements into an OpenMCL Listener the same error results. Does anyone know if this error is a genuine bug, or is there something else missing in the loading sequence I describe above. I am aware that the beagle back-end is experimental, but my aim is to be able to reproduce some of the screen-shots of mcclim using the beagle back-end which available on the web. Thanks.

3 5