mcclim-devel March 2006

mcclim-devel@common-lisp.net

20 participants
42 discussions

[mcclim-devel] Please remove debian/ from CVS
by Milan Zamazal 27 Mar '06

27 Mar '06

Would you please remove the debian/ directory (or at least its contents) from CVS? The files there are obsolete, the package is maintained in Debian properly. Thank you. Regards, Milan Zamazal -- http://www.zamazal.org

1 0

[mcclim-devel] fix for remove-command-from-command-table
by Vincent Arkesteijn 23 Mar '06

23 Mar '06

Hi, At present, remove-command-from-command-table doesn't, except for menu-items. The attached patch fixes that. Vincent.

2 3

[mcclim-devel] Patch: CLIM-SYS:MAKE-PROCESS fix for SBCL
by Troels Henriksen 23 Mar '06

23 Mar '06

CLIM-SYS:MAKE-PROCESS doesn't pass on the specified process name to SB-THREAD:MAKE-THREAD under SBCL, resulting in unnamed threads. The attached simple patch fixes this. Index: Lisp-Dep/mp-sbcl.lisp =================================================================== RCS file: /project/mcclim/cvsroot/mcclim/Lisp-Dep/mp-sbcl.lisp,v retrieving revision 1.8 diff -u -r1.8 mp-sbcl.lisp --- Lisp-Dep/mp-sbcl.lisp 15 Jul 2005 16:36:58 -0000 1.8 +++ Lisp-Dep/mp-sbcl.lisp 23 Mar 2006 13:16:55 -0000 @@ -76,7 +76,7 @@ (let ((*current-process* p)) (funcall (process-function p) )))) (when (process-thread p) (sb-thread:terminate-thread p)) - (when (setf (process-thread p) (sb-thread:make-thread #'boing)) + (when (setf (process-thread p) (sb-thread:make-thread #'boing :name (process-name p))) p))) (defun destroy-process (process) -- \ Troels "Athas" Henriksen /\ - Insert witty signature

1 0

[mcclim-devel] Patch for CLX backend `medium-draw-ellipse*'-bug
by Troels Henriksen 23 Mar '06

23 Mar '06

This email relates to the bug described in: http://common-lisp.net/pipermail/mcclim-devel/2005-December/004334.html I believe I have located the bug in Backends/CLX/medium.lisp, in the method `medium-draw-ellipse*'. Basically, the method assumes that if `end-angle' is negative, it will be necessary to add 2pi radians to the arc angle to make sure the arc will be drawn counter-clockwise (as the CLIM spec specifies), but this is not the case if start-angle is negative or 0 as well. The attached patch fixes this issue, but it does not make McCLIM do as the bug reporter expects. The arc is vertically mirrored with respect to the expected location, but as far as I can see from the spec, this is actually where it should be placed, due to the negative scale-y argument to `with-scaling' - could this be a bug in the LispWorks implementation? In any case, erroneous positioning of the arc is probably not related to to the function I have patched, so it should be safe to commit. Index: Backends/CLX/medium.lisp =================================================================== RCS file: /project/mcclim/cvsroot/mcclim/Backends/CLX/medium.lisp,v retrieving revision 1.72 diff -u -r1.72 medium.lisp --- Backends/CLX/medium.lisp 17 Feb 2006 14:16:39 -0000 1.72 +++ Backends/CLX/medium.lisp 12 Mar 2006 19:58:01 -0000 @@ -564,7 +564,8 @@ (with-transformed-position ((sheet-native-transformation (medium-sheet medium)) center-x center-y) (let* ((arc-angle (- end-angle start-angle)) - (arc-angle (if (< end-angle 0) + (arc-angle (if (and (< end-angle 0) + (>= start-angle 0)) (+ (* pi 2) arc-angle) arc-angle))) (with-clx-graphics (medium) -- \ Troels "Athas" Henriksen /\ - Insert witty signature

2 2

[mcclim-devel] Patch: method browser, use clim-mop for portability.
by Douglas Crosher 23 Mar '06

23 Mar '06

* method-browser (eql-specializer-p, eql-specializer-object): remove these local definitions and use clim-mop:eql-specializer and clim-mop:eql-specializer-object for better portability. * method-browser (classp): special case for the Scieneer CL. Regards Douglas Crosher Index: Examples/method-browser.lisp =================================================================== RCS file: /project/mcclim/cvsroot/mcclim/Examples/method-browser.lisp,v retrieving revision 1.2 diff -u -r1.2 method-browser.lisp --- Examples/method-browser.lisp 6 Mar 2005 20:35:40 -0000 1.2 +++ Examples/method-browser.lisp 16 Mar 2006 01:49:58 -0000 @@ -69,21 +69,14 @@ (defun classp (x) (or (typep x 'cl:class) - #+CMU (typep x 'pcl::class))) - -(defun eql-specializer-p (x) - #+SBCL (typep x 'sb-mop:eql-specializer) - #+CMU (typep x 'pcl:eql-specializer)) - -(defun eql-specializer-object (x) - #+SBCL (sb-mop:eql-specializer-object x) - #+CMU (pcl::eql-specializer-object x)) + #+CMU (typep x 'pcl::class) + #+scl (typep x 'clos::std-class))) (defun compute-applicable-methods-from-specializers (gf specializers) (clim-mop:compute-applicable-methods gf (mapcar (lambda (spec) - (cond ((eql-specializer-p spec) - (eql-specializer-object spec)) + (cond ((typep spec 'clim-mop:eql-specializer) + (clim-mop:eql-specializer-object spec)) ((classp spec) (clim-mop:class-prototype spec)) (t (error "Can't compute effective methods, specializer ~A is not understood." spec))))

2 1

[mcclim-devel] Freeze period start for McCLIM 0.9.2
by Andreas Fuchs 22 Mar '06

22 Mar '06

Hi all, This mail marks the start of the freeze period for McCLIM 0.9.2. As you know, the plan is to release 0.9.2 on the next Sunday, the March 19th. In the meantime, please test on as many platforms and lisp implementations as possible. Post results, both negative and positive, to mcclim-devel. Also, I encourage you all to fix bugs and post fixes to mcclim-devel for review. Cheers, -- Andreas Fuchs, (http://|im:asf@|mailto:asf@)boinkor.net, antifuchs

4 11

[mcclim-devel] patches to guided-tour subsection "A Simple drawing application"
by rpgoldman＠real-time.com 19 Mar '06

19 Mar '06

Again, mostly just tweaking grammar and spelling. There are two points below (marked with my initials), however, that seem like they could use some further clarification. I was concerned that I didn't understand McCLIM well enough to provide the clarification. If anyone out there can provide the clarification, but doesn't want to dicker with the text, drop me a line, or find me on #lisp, and I'll write the text. As usual, if I don't hear a squawk in a couple of days, I'll commit the change. best, R P.S. are these patch files really helpful for the text? In particular, is it useful to have my notes on places where we need clarification from their contexts untimely ripp'd? If I provide a comment saying that a paragraph could use amplification, and you see that in a patch file w/o context, is that at all useful to anyone? Index: guided-tour.tex =================================================================== RCS file: /project/mcclim/cvsroot/mcclim/Doc/Guided-Tour/guided-tour.tex,v retrieving revision 1.3 diff -c -r1.3 guided-tour.tex *** guided-tour.tex 16 Mar 2006 15:50:20 -0000 1.3 --- guided-tour.tex 19 Mar 2006 15:56:21 -0000 *************** *** 991,997 **** \subsection{A simple drawing application} ! We move on to a simple drawing application that draws lines and inserts text interactively. Our simple drawing program defines commands for various drawing operations and binds specific input events to these commands. --- 991,997 ---- \subsection{A simple drawing application} ! We move on to a simple application that draws lines and inserts text interactively. Our simple drawing program defines commands for various drawing operations and binds specific input events to these commands. *************** *** 1005,1010 **** --- 1005,1015 ---- multiple layouts with this option. We define two simple layouts, \code{default-layout} and \code{alternative}. + % I was confused by the discussion of layouts here. Looking at Figure + % 4, I do not see an alternative layout, and the default-default in + % the listing looks odd to me. Is this the remainder of a discussion + % that was deleted or an extension yet to be written? [2006/03/19:rpg] + \begin{figure*}[t] \lstset{style=framestyle} \lstinputlisting{draw-frame-commands} *************** *** 1048,1055 **** static user interfaces use this mixin. Note that \mcclim{} is sensitive to the order of the superclasses.\footnote{All stream classes like \class{standard-extended-input-stream} must be listed before ! \class{basic-pane}. Otherwise, there are no stream handling facilities ! available.} For \class{draw-pane}, the \method{handle-repaint} method shown in \figurename~\ref{fig-draw-handlerepaint} is straightforward. It --- 1053,1070 ---- static user interfaces use this mixin. Note that \mcclim{} is sensitive to the order of the superclasses.\footnote{All stream classes like \class{standard-extended-input-stream} must be listed before ! \class{basic-pane}. Otherwise, no stream handling facilities ! will be available.} ! ! % The above footnote refers to what looks like a very big potential ! % ``gotcha'' for the beginning McCLIM programmer. Suggestion: promote ! % this out of the footnote into body text as a main body paragraph ! % here. That paragraph should explain (1) why is it that putting ! % basic-pane before standard-extended-input-stream will cause stream ! % handling facilities to be crushed and (2) what exactly are the ! % implications of not having stream handling facilities. The phrase ! % ``stream handling'' hasn't been defined, and it's not obvious what ! % these facilities are. [2006/03/19:rpg] For \class{draw-pane}, the \method{handle-repaint} method shown in \figurename~\ref{fig-draw-handlerepaint} is straightforward. It *************** *** 1085,1125 **** conveniently. The interactor pane can be used to invoke one of three commands, either by typing the complete command including all its parameters or by typing only the command name, then a dialog queries ! the user for the missing command argument. Clicking on the menu bar ! entries is also possible. Also in this case, the user is queried for ! the missing arguments. But drawing by typing coordinates is not convenient. Therefore, we attach these commands to other user interactions. Figure ! \ref{fig-draw-interfacing} defines input methods for pointer button ! presses as well as key presses on the draw pane. Both handlers invoke ! the respective tracking function that uses \macro{tracking-pointer} to bypass the regular input distribution channels and to dispatch events to user defined handlers. ! ! For \class{pointer-button-press-event}, the input loop manages a ! ``rubber-banding'' line. The \keyword{:pointer-motion} is invoked whenever the mouse pointer is moved by the user. The code attached to ! \keyword{:pointer-motion} clears line already drawn and draws a new line with the new pointer position. It can easily undraw the old line by the using the special ink \constant{+flipping-ink+}. When the user confirms the line by releasing the pointer button, a command to the application is synthesized via \method{execute-frame-command} supplying all required parameters. ! Similarly, we provide such an input facility for text input. Whenever the user hits a key in the draw-pane, the respective \method{handle-event} calls \method{track-text-drawing} which attaches ! the character entered to the mouse pointer. Similarly to the ! rubber-banding line, the user can move the around this character while he is free to append additional string characters by additional key presses. He can confirm the text position with a mouse click causing a ! command to be dispatched to the application frame adding the text to the application frame permanently. As each of these methods invoke \code{execute-frame-command} passing ! in a special command invocation form, this naturally leads to code ! separation of how a command is invoked (menu-bar click, click on draw-pane or typing in the interactor pane) and the code for command execution (code bodies of \method{define-command}). --- 1100,1160 ---- conveniently. The interactor pane can be used to invoke one of three commands, either by typing the complete command including all its parameters or by typing only the command name, then a dialog queries ! the user for the missing command argument(s). Clicking on the menu bar ! entries is another way to invoke commands. When commands are invoked ! through the menu bar, the user will be queried for the missing ! argument(s) in the same way as if a command had been typed into the ! interactor pane. ! % also possible. Also in this case, the user is queried for ! % the missing arguments. But drawing by typing coordinates is not convenient. Therefore, we attach these commands to other user interactions. Figure ! \ref{fig-draw-interfacing} defines input methods (methods for ! \code{handle-event}) for pointer button ! presses as well as key presses on the draw pane. ! Each handler invokes a tracking function (\code{track-line-drawing} and ! \code{track-text-drawing}) that uses \macro{tracking-pointer} to bypass the regular input distribution channels and to dispatch events to user defined handlers. ! % old text: [2006/03/19:rpg] ! % Both handlers invoke ! % the respective tracking function that uses \macro{tracking-pointer} to ! % bypass the regular input distribution channels and to dispatch events ! % to user defined handlers. ! ! For \class{pointer-button-press-event}, which is used to draw lines, ! the input loop manages a ! ``rubber-banding'' line. % ! % what is pointer-motion here? Is it an event? And it's not really ! % the event that's invoked, to be absolutely clear. The event is ! % signaled, and the tracking-pointer macro provides a handler for that ! % event. So it is the code associated with :pointer-motion that is ! % invoked... I wasn't confident enough in my understanding of the ! % precise organization of the (Mc)CLIM architecture to venture a ! % rewrite, but there should be a clarification here. [2006/03/19:rpg] ! The \keyword{:pointer-motion} is invoked whenever the mouse pointer is moved by the user. The code attached to ! \keyword{:pointer-motion} clears the previously-drawn line and draws a new line with the new pointer position. It can easily undraw the old line by the using the special ink \constant{+flipping-ink+}. When the user confirms the line by releasing the pointer button, a command to the application is synthesized via \method{execute-frame-command} supplying all required parameters. ! We provide a similar input facility for text input. Whenever the user hits a key in the draw-pane, the respective \method{handle-event} calls \method{track-text-drawing} which attaches ! the character entered to the mouse pointer. As with the ! rubber-banding line, the user can move the displayed string around while he is free to append additional string characters by additional key presses. He can confirm the text position with a mouse click causing a ! command to be dispatched to the application frame that will add the text to the application frame permanently. As each of these methods invoke \code{execute-frame-command} passing ! in a special command invocation form, this naturally leads to a ! separation between the code that specifies how a command is invoked (menu-bar click, click on draw-pane or typing in the interactor pane) and the code for command execution (code bodies of \method{define-command}).

1 0

[mcclim-devel] SPATIAL-TREES not found
by idurand＠labri.fr 17 Mar '06

17 Mar '06

Hi, Tonight, friday March 17th, I tried to recompile my cvs updated version of mcclim and it won't compile. I am using OpenMCL on MACOSX. For now, how can I go back to an older but working version? Irène component :SPATIAL-TREES not found, required by #<SYSTEM "clim-core" #x64418F6> [Condition of type ASDF:MISSING-DEPENDENCY] Restarts: 0: [ABORT-REQUEST] Abort handling SLIME request. 1: [ABORT-BREAK] #<RESTART ABORT-BREAK #x65BE06> 2: [ABORT] #<RESTART ABORT #x65BE2E> Backtrace: 0: (ASDF::DO-ONE-DEP #<COMPILE-OP NIL #x6548656> #<SYSTEM "clim-core" #x64418F6> 'ASDF:COMPILE-OP ':SPATIAL-TREES 'NIL) 1: (ASDF::DO-DEP #<COMPILE-OP NIL #x6548656> 'NIL #<SYSTEM "clim-core" #x64418F6> '(:SPATIAL-TREES :CLIM-LISP) #<SYSTEM "clim-core" #x64418F6>) 2: (#<STANDARD-METHOD ASDF::TRAVERSE (ASDF:OPERATION ASDF:COMPONENT)> ':CLIM-CORE 'NIL) 3: (ASDF::DO-DEP #<COMPILE-OP NIL #x6548A16> 'NIL #<SYSTEM "clim-postscript" #x645B8CE> '(:CLIM-CORE) #<SYSTEM "clim-postscript" #x645B8CE>) 4: (#<STANDARD-METHOD ASDF::TRAVERSE (ASDF:OPERATION ASDF:COMPONENT)> ':CLIM-POSTSCRIPT '(:GOATEE-CORE :CLIM-CORE)) 5: (ASDF::DO-DEP #<COMPILE-OP NIL #x6497A9E> 'NIL #<SYSTEM "clim" #x64517EE> '(:CLIM-POSTSCRIPT :GOATEE-CORE :CLIM-CORE) #<SYSTEM "clim" #x64517EE>) 6: (#<STANDARD-METHOD ASDF::TRAVERSE (ASDF:OPERATION ASDF:COMPONENT)> ':CLIM 'NIL) 7: (ASDF::DO-DEP #<COMPILE-OP NIL #x64805D6> '((#1=#<LOAD-OP NIL #x64945E6> . #<CLX-SOURCE-FILE "package" #x648B976>) (#1# . #<CLX-SOURCE-FILE "depdefs" #x648B5DE>) (#1# . #<CLX-SOURCE-FILE "clx" #x648B20E>) (#1# . #<CLX-SOURCE-FILE "dep-openmcl" #x648AE26>) (#1# . #<CLX-SOURCE-FILE "macros" #x648AA26>) (#1# . #<CLX-SOURCE-FILE "bufmac" #x648A60E>) (#1# . #<CLX-SOURCE-FILE "buffer" #x648A1DE>) (#1# . #<CLX-SOURCE-FILE "display" #x6489D96>) (#1# . #<CLX-SOURCE-FILE "gcontext" #x6489936>) (#1# . #<CLX-SOURCE-FILE "input" #x64894BE>) ...) #<SYSTEM "clim-clx" #x645B12E> '(:CLX :CLIM) #<SYSTEM "clim-clx" #x645B12E>) 8: (#<STANDARD-METHOD ASDF::TRAVERSE (ASDF:OPERATION ASDF:COMPONENT)> ':CLIM-CLX '(:CLIM)) 9: (ASDF::DO-DEP #<COMPILE-OP NIL #x6480616> 'NIL #<SYSTEM "clim-looks" #x646209E> '(:CLIM-CLX :CLIM) #<SYSTEM "clim-looks" #x646209E>) 10: (#<STANDARD-METHOD ASDF::TRAVERSE (ASDF:OPERATION ASDF:COMPONENT)> ':CLIM-LOOKS 'NIL) 11: (ASDF::DO-DEP #<COMPILE-OP NIL #x64808BE> 'NIL #<SYSTEM "mcclim" #x6478676> '(:CLIM-LOOKS) #<SYSTEM "mcclim" #x6478676>) 12: (#<STANDARD-METHOD ASDF::TRAVERSE (ASDF:OPERATION ASDF:COMPONENT)> "mcclim" 'NIL) 13: (ASDF::DO-DEP #<LOAD-OP NIL #x644006E> 'NIL #<SYSTEM "mcclim" #x6478676> '("mcclim") #<SYSTEM "mcclim" #x6478676>) 14: (#<STANDARD-METHOD ASDF::TRAVERSE (ASDF:OPERATION ASDF:COMPONENT)> #<CONNECTION #x6438D36> #<TWO-WAY-STREAM input #<SWANK-BACKEND::SLIME-INPUT-STREAM #x6436A7E>, output #<TCP-STREAM (SOCKET/8) #x6438BC6> #x64363C6>) 15: (ASDF:OPERATE 'ASDF:LOAD-OP ':MCCLIM) 16: (CCL::CALL-CHECK-REGS 'ASDF:OPERATE) 17: (#<Anonymous Function #x6404BA6> "(asdf:operate 'asdf:load-op :mcclim)") 18: (SWANK::CALL-WITH-BUFFER-SYNTAX #<COMPILED-LEXICAL-CLOSURE #x64400DE>) 19: (CCL::CALL-CHECK-REGS 'SWANK:INTERACTIVE-EVAL) 20: (#<Anonymous Function #x640538E> '(SWANK:INTERACTIVE-EVAL "(asdf:operate 'asdf:load-op :mcclim)") 2 'NIL) 21: (#<STANDARD-METHOD SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK (T T)> #<Compiled-function SWANK:SWANK-DEBUGGER-HOOK #x6409C36> #<COMPILED-LEXICAL-CLOSURE #x64400FE>) 22: (FUNCALL 'SWANK::EVAL-FOR-EMACS) 23: (#<Anonymous Function #x63ECE86>) 24: (#<Anonymous Function #x63E639E> #<Anonymous Function #x63ECE86>) 25: (SWANK::CALL-WITH-REDIRECTED-IO #<COMPILED-LEXICAL-CLOSURE #x644011E> 'NIL) 26: (SWANK::CALL-WITH-CONNECTION #<CONNECTION #x6438D36> #<Anonymous Function #x63ECE86>) 27: (SWANK::HANDLE-REQUEST #<CONNECTION #x6438D36>) 28: (SWANK::CALL-WITH-BINDINGS 'NIL #<COMPILED-LEXICAL-CLOSURE #x6440136>) 29: (CCL::RUN-PROCESS-INITIAL-FORM '(#<COMPILED-LEXICAL-CLOSURE #x64392C6>) #<PROCESS worker(7) [Active] #x64392FE>) 30: (#<Anonymous Function #x6101D3E> '(#<COMPILED-LEXICAL-CLOSURE #x64392C6>) 0) 31: (#<Anonymous Function #x60F491E> 265728 #<LISP-THREAD worker [tcr @ #x103800] #x64393E6>) ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

2 1

[mcclim-devel] Patch: xrender request type arguments corrections.
by Douglas Crosher 17 Mar '06

17 Mar '06

* xrender.lisp (render-composite, render-composite-glyphs-8, %render-composite-glyphs): correct some of the request type arguments: CARD16 to INT16. Fixes types errors when using freetype. Regards Douglas Crosher Index: Experimental/freetype/xrender.lisp =================================================================== RCS file: /project/mcclim/cvsroot/mcclim/Experimental/freetype/xrender.lisp,v retrieving revision 1.2 diff -u -r1.2 xrender.lisp --- Experimental/freetype/xrender.lisp 2 Dec 2004 09:11:41 -0000 1.2 +++ Experimental/freetype/xrender.lisp 16 Mar 2006 01:31:05 -0000 @@ -719,12 +719,12 @@ (resource-id (picture-id source)) (resource-id (if mask (picture-id mask) 0)) (resource-id (picture-id dest)) - (card16 src-x) - (card16 src-y) - (card16 mask-x) - (card16 mask-y) - (card16 dst-x) - (card16 dst-y) + (int16 src-x) + (int16 src-y) + (int16 mask-x) + (int16 mask-y) + (int16 dst-x) + (int16 dst-y) (card16 width) (card16 height)))) @@ -787,7 +787,7 @@ (int16 src-x) (int16 src-y) (card8 (- end start)) ;length of glyph elt (card8 0) (card16 0) ;padding - (card16 dest-x) (card16 dest-y) ;dx, dy + (int16 dest-x) (int16 dest-y) ;dx, dy ((sequence :format card8) sequence)))) (defmacro %render-composite-glyphs @@ -804,7 +804,7 @@ (int16 ,src-x) (int16 ,src-y) (card8 (- ,end ,start)) ;length of glyph elt (card8 0) (card16 0) ;padding? really? - (card16 ,dest-x) (card16 ,dest-y) ;dx, dy + (int16 ,dest-x) (int16 ,dest-y) ;dx, dy ((sequence :format ,type :start ,start :end ,end :transform ,transform) ,sequence))) (defun render-composite-glyphs (dest glyph-set source dest-x dest-y sequence

2 1

[mcclim-devel] scigraph and out-of-the-boxness
by Christophe Rhodes 17 Mar '06

17 Mar '06

Hi, I attach a patch which lets scigraph build out of the box for me under sbcl. I don't think I'm likely to have broken any other configuration, but maybe someone would like to look at this? Cheers, Christophe

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

mcclim-devel March 2006