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

Compiling/installing McCLIM on LispWorks 6.1 Professional Edition
by Sian Mountbatten 08 Apr '15

08 Apr '15

Dear List I have tried to load McCLIM onto my copy of LispWorks and have discovered the following error: In the file mcclim-20140316-git/Lisp-Dep/fix-lispworks.lisp, the last form is (defmethod clim-mop:class-direct-superclasses ((instance (eql *ptype-t-class*))) (list (find-class 'standard-object))) ;; scary.. I have discovered that *ptype-t-class* is defined in file presentations.lisp (line 754), but is nowhere given a value. Thus the parameter "instance" of the method defined above cannot be specialized on *ptype-t-class*. Please would you advise me on how to get mcclim loaded into lispworks. Your sincerely -- Dr Sian Mountbatten http://www.poenikatu.co.uk/ Associate member of the FSF no. 10888 Asocia membro de la Libera Programara Fonduso n-ro 10888

1 0

The only way to regain your intimate life
by Tom Hahn 08 Apr '15

08 Apr '15

Make your woman pleased http://www.filus66.user.icpnet.pl/rate.html

1 0

[mcclim-devel] button size
by Irène Durand 27 Mar '13

27 Mar '13

> ------------------------------ > > Message: 2 > Date: Wed, 27 Mar 2013 10:05:48 -0300 > From: Mariano Montone<marianomontone(a)gmail.com> > To: mcclim-devel(a)common-lisp.net > Subject: Re: [mcclim-devel] button size > Message-ID:<5152EEAC.7040909(a)gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi. > > Did you try with :x-spacing and :y-spacing instead of :width and :height > to see what happens? I just did. The button is bigger but it is still not a square. I guess that I will have to try what Andy suggested: write a new compose-space method :-( Irène > Mariano > > El 27/03/13 09:22, Ir?ne Durand escribi?: >> Hello, >> >> In order to give a project to my students using McClim for the graphical >> interface, I am trying to make a square button of a given size. >> >> But I always obtain a default size button the width, height, >> max-width, ... >> have no effect. >> >> Where could I find some help about that? >> >> Thank you, >> Ir?ne >> >> (defun make-square-pane () >> (make-pane >> 'square-button-pane >> :label "" >> :width 20 >> :height 20 >> :activate-callback (lambda (x) >> (setf (gadget-label x) "O")))) >> >> >> >> >> _______________________________________________ >> mcclim-devel mailing list >> mcclim-devel(a)common-lisp.net >> http://lists.common-lisp.net/cgi-bin/mailman/listinfo/mcclim-devel >

1 0

Re: [mcclim-devel] mcclim-devel Digest, Vol 39, Issue 6
by Irene DURAND 27 Mar '13

27 Mar '13

Hello, As my paste on irc lisp, did not have any answer, I turning again to this more specialized mailing list. I have this MClim problem. The application runs fine on Linux with SBCL 1.0.13, xorg-x11-server 1.3.0.0-9.fc7, a recent version of MClim. But doesn't on my Mac (Darwin PowerPC) with MacOS 10.5 (leopard), SBCL 1.0.16, cvs version of MClim, Xquartz 2.1.5 - (xorg-server 1.3.0-apple22)(2.1.5). I have tried to create the smallest as possible application where the problems occurs (attached). Just compile the file and launch mini::(start) On Linux, I have the desired behaviour: a circle blinks (red/green/red/...) on the display pane and at the bottom of the window application, the "quit" button is displayed and works. On the Mac, the circle blinks correctly but the "Quit" button never shows up. For a while the application is killable with C-c C-c (under Slime), but after a while there is no way to kill it than to stop Lisp and restart everything (even /the/ <http://www.lispworks.com/reference/HyperSpec/Body/s_the.htm> X server). Note that this application used to work on Mac OS 10.3 (Panther) with older versions of everything. I suspect the X server to behave differently from before. But now I don't see how to make the application work. This is too bad, as I usually use a similar application for my Lisp undergraduate course. If anyone has an idea, it will be welcomed. Irène (defpackage :mini (:use :clim :clim-extensions :clim-lisp)) (in-package :mini) (let ((colors (list +red+ +green+))) (setf colors (nconc colors colors)) (defun display-function (frame pane) (draw-circle* pane 10 10 10 :ink (pop colors)) (sleep 0.5) (redisplay-frame-panes frame))) (defun quit () (frame-exit *application-frame*)) (define-application-frame mini () () (:panes (display :application :display-function 'display-function :incremental-redisplay t) (quit :push-button :label "Quit" :activate-callback (lambda (x) (declare (ignore x)) (quit)))) (:layouts (defaults (vertically () display quit)))) (defun run-test (name) (loop for port in climi::*all-ports* do (destroy-port port)) (setq climi::*all-ports* nil) (let ((frame (make-application-frame name))) (run-frame-top-level frame))) (defun start () (run-test 'mini) 0) (defmethod run-frame-top-level :before ((mini mini) &key) (let* ((frame-manager (frame-manager *application-frame*)) (port (climi::frame-manager-port frame-manager)) (display (clim-clx::clx-port-display port))) (setf (xlib:display-after-function display) g#'xlib:display-force-output)))

4 4

Re: [mcclim-devel] mcclim failure with asdf3
by Anton Vodonosov 27 Feb '13

27 Feb '13

In addition, mcclim and all the dependent systems fail on CLISP and Allegro with ASDF3 because .asd file tries to define a method for asdf:traverse generic function. The method signature is incompatible with the generic function anymore - doesn't have &REST or &KEY. Best regards, - Anton

2 3

[mcclim-devel] mcclim failure with asdf3
by Faré 27 Feb '13

27 Feb '13

ASDF3 now checks deferred warnings by default, which notably catches forward references to special variables. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org If the Bible proves that God exists then comic books prove the existence of Superman. — seen on #Atheism IRC ; file: /home/testgrid/quicklisp-patched2/dists/quicklisp/software/mcclim-20120909-cvs/graphics.lisp ; in: CLIM-EXTENSIONS:DEFINE-BITMAP-FILE-READER :XPM ; (CLIM-INTERNALS::XPM-PARSE-FILE PATHNAME) ; ; caught STYLE-WARNING: ; undefined function: CLIM-INTERNALS::XPM-PARSE-FILE ; ; compilation unit finished ; Undefined types: ; CLIM:CLIM-STREAM-PANE CLIM:STREAM-OUTPUT-HISTORY-MIXIN CLIM-INTERNALS::TOP-LEVEL-SHEET-PANE ; Undefined functions: ; (SETF CLIM-BACKEND:PORT-MOTION-HINTS) (SETF CLIM-BACKEND:SELECTION-OWNER) (SETF CLIM-BACKEND:SELECTION-TIMESTAMP) CLIM-LISP:DESCRIBE CLIM:MAKE-SPACE-REQUIREMENT CLIM:MEDIUM CLIM-BACKEND:PORT-MOTION-HINTS CLIM-BACKEND:PORT-SET-MIRROR-REGION CLIM-BACKEND:PORT-SET-MIRROR-TRANSFORMATION CLIM-BACKEND:SELECTION-OWNER CLIM-INTERNALS::TEXT-BOUNDING-RECTANGLE* CLIM-INTERNALS::XPM-PARSE-FILE ; Undefined variables: ; CLIM:*INPUT-WAIT-HANDLER* CLIM:*INPUT-WAIT-TEST* CLIM:*POINTER-BUTTON-PRESS-HANDLER* CLIM:+EVERYWHERE+ CLIM:+NOWHERE+ ; caught 7 WARNING conditions ; caught 35 STYLE-WARNING conditions Unhandled SERIOUS-CONDITION of type COMPILE-FAILED-ERROR is signaled: Lisp compilation failed

1 1

[mcclim-devel] XRender opacity
by Manuel Giraud 19 Dec '12

19 Dec '12

Hi, Here is a patch (that apply against the official CVS repo) with a minor correction and a test case (implemented in the clim-fig example) of XRender rectangle opacity. I'd like to make other routines (medium-draw-polygon*, medium-draw-ellipse*,...) to use the XRender extension. So far, I've tested cl-geometry (https://github.com/Ramarren/cl-geometry) that can decompose a polygon as triangles that can then be feed to xlib:render-triangles-1. Is there any advice (other than "use the gtkairo backend")? -- Manuel Giraud

1 0

[mcclim-devel] how to track down apparent memory leaks in drawing?
by John Morrison 14 Nov '12

14 Nov '12

Hi All; tl:dr; slightly revised drawing-benchmark demo (attached) from quicklisp mcclim shows increased (leaked?) memory usage. I am using McCLIM to deal with PostGIS (FC16, x86_64). It appeared that drawing vector GIS data using draw-line* leaked memory. After doing the obvious things (see below), I slightly modified the clim-demo::drawing-benchmark app to try and produce the smallest code that exhibits the behavior: 1. draw lines instead of either rectangles or text 2. for 20 seconds rather than 1 3. print SBCL's (room) into the window (make your mapped window tall) 4. run a (sb-ext:gc) 5. print (room) again lather, rinse, and repeat, by hitting the "Run" button. I obviously didn't use the presentation system in my program (as I presumed it would hold onto output records, etc.). I commented out the single draw-line* form, and that enabled my program to traverse the entire (rather large) GIS vector dataset with no perceptible increase in memory usage (according to the "top" UNIX utility rather than (room). I updated to today's SBCL (maybe it's a bug that's been fixed), but I still observed the increasing memory usage. Questions: (a) Should I try any of the several forked McCLIMs mentioned recently? Has any of them had significant work in the simple drawing area? (b) Can anybody tell me anything that might shorten the hunt? Thanks!!! -jm -- --- John Morrison --- john.nmi.morrison(a)gmail.com

1 1

[mcclim-devel] Official repository lagging?
by Manuel Giraud 14 Nov '12

14 Nov '12

Hi mcclimers, I wanted to (re)try to do some hacking on mcclim. So I have checkout the official CVS repository (from which the quicklisp package seems to be made of) and (slowly) start working on it. Then it occured to me there are many public fork of mcclim on github, for instance: https://github.com/onixie/mcclim https://github.com/slyrus/mcclim https://github.com/mmontone/mcclim https://github.com/timoore/mcclim All of them were active in the last 4 months and have their own set of improvements while the official CVS last patch dates back to july 2011. So my question is, can someone with enough credential collects (and maybe selects) those patches and apply them to the official repository? (I know I can 'git clone' one of those repo, cherry pick what I want and add my patches but then it will be yet another unofficial repo). Best, -- Manuel Giraud

6 8

[mcclim-devel] prompt-for-items-from-list with list-pane
by Kilian Sprotte 31 Oct '12

31 Oct '12

Hi, I made a simple implementation of prompt-for-items-from-list. Any comments? In particular, I am wondering if :items *items* using a special variable is the only way to initialize the list-pane. Regards, Kilian (defvar *items*) (define-application-frame items-from-list () ((exit-command :accessor exit-command)) (:menu-bar t) (:panes (list (make-pane 'list-pane :mode :nonexclusive :items *items*))) (:layouts (default (scrolling (:scroll-bar :vertical) list)))) (macrolet ((frob (command) `(define-items-from-list-command (,command :name t :menu t) () (setf (exit-command *application-frame*) ',command) (frame-exit *application-frame*)))) (frob com-ok) (frob com-cancel)) (defun prompt-for-items-from-list (items) (flet ((get-list-pane (frame) (find-pane-named frame 'list))) (let* ((*items* items) (frame (make-application-frame 'items-from-list))) (run-frame-top-level frame) (ecase (exit-command frame) (com-ok (values (gadget-value (get-list-pane frame)) t)) (com-cancel (values nil nil))))))

2 1