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

[mcclim-devel] clim-debugger
by Peter Mechlenborg 26 Apr '05

26 Apr '05

Hi all I finally took some time off to do a bit on the debugger again. It can be found here: http://www.daimi.au.dk/~metch/lisp/clim-debugger.lisp Changes: - A "more button" have been added, so more stack-frames can be viewed if 20 isn't enough. - Scroll-bars have been added, thanks to Elliott Johnson. There's still a small problem though. The scroll-bars do not remember their position when a stack-frame or "more" is pressed. I don't know how to fix this, couldn't find anything in the specs and Clouseau didn't help either. Do anyone of you know how to do this? - Frame variables are viewed with Clouseau when pressed. What do you think? Have fun, -- Peter

5 8

[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] How to change color of a text field
by Paolo Amoroso 21 Apr '05

21 Apr '05

How can I change the color of the text displayed in a text field? Does the CLIM specification allow this? Paolo -- Lisp Propulsion Laboratory log - http://www.paoloamoroso.it/log

3 6

[mcclim-devel] keymap switching in McCLIM frame
by glitch 20 Apr '05

20 Apr '05

I heard that i probably get help in this mailing list. I have stumbled on problem with keymap switching in McCLIM frames. What i did: $ clim * (some-loading) * (run-frame-top-level 'any-frame) -> user gesture, that causes setxkbmap -> no reaction ^C (ext:quit) $ clim * (run-frame-top-level 'any-frame) -> typing any keys *trace-output*: lookup-gesture-command: 0 :|cyrillic-<something>| - why now? cmucl19a clx5.2 McCLIM 0.9 Excuse me please for my broken English :( best regards /glitch

1 0

[mcclim-devel] keymap switching in McCLIM frame
by glitch 20 Apr '05

20 Apr '05

I heard that i probably get help in this mailing list. I have stumbled on problem with keymap switching in McCLIM frames. What i did: $ clim * (some-loading) * (run-frame-top-level 'any-frame) -> user gesture, that causes setxkbmap -> no reaction ^C (ext:quit) $ clim * (run-frame-top-level 'any-frame) -> typing any keys *trace-output*: lookup-gesture-command: 0 :|cyrillic-<something>| - why now? cmucl19a clx5.2 McCLIM 0.9 Excuse me please for my broken English :( best regards /glitch

1 0

[mcclim-devel] mcclim.asd patch for Allegro CL
by rpgoldman＠real-time.com 18 Apr '05

18 Apr '05

Here's a patch that causes Allegro (or at least my beloved, increasingly aged ACL 6.2), to load CLX while loading MCCLIM. Per Christophe's instructions on #lisp, consider this to be an official whine to have the patch applied! :-) I don't believe that there's any way this could muck things up for anyone not using ACL, but I am not infallible... R --- mcclim.asd 1 Mar 2005 15:46:13 -0000 1.4 +++ mcclim.asd 18 Apr 2005 17:19:18 -0000 @@ -80,6 +80,25 @@ (defsystem :clim-lisp #+clisp "fix-clisp"))) (:file "package" :depends-on ("Lisp-Dep")))) +;;; possibly this should be further refined to funciton properly for +;;; Allegro on Windows platforms. [2005/04/18:rpg] +#+allegro +(defclass requireable-system (asdf:system) + () + ) + +#+allegro +(defmethod asdf:perform ((op asdf:load-op) (system requireable-system)) + (require (intern (slot-value system 'asdf::name) "KEYWORD"))) + +#+allegro +(defmethod asdf::traverse ((op asdf:load-op) (system requireable-system)) + (list (cons op system))) + +#+allegro +(defsystem :clx + :class requireable-system) + (defsystem :clim-core :depends-on (:clim-lisp) :components ((:file "decls") @@ -216,7 +235,7 @@ (defsystem :clim )) (defsystem :clim-clx - :depends-on (:clim #+(or sbcl openmcl ecl) :clx) + :depends-on (:clim #+(or sbcl openmcl ecl allegro) :clx) :components ((:module "Backends/CLX" :pathname #.(make-pathname :directory '(:relative "Backends" "CLX")) @@ -276,7 +295,7 @@ (defsystem :clim-looks :depends-on (:clim ;; If we're on an implementation that ships CLX, use ;; it. Same if the user has loaded CLX already. - #+(or sbcl openmcl ecl clx) :clim-clx + #+(or sbcl openmcl ecl clx allegro) :clim-clx #+gl :clim-opengl ;; OpenMCL and MCL support the beagle backend (native ;; OS X look&feel on OS X).

1 0

[mcclim-devel] error on modifying example code
by Jason Wang 16 Apr '05

16 Apr '05

hi, i just got McClim and see how it works.. and got my first attempt in modifying the example code(s) in trying to get a feel how everything works.. though, what seem to be a simple layout edition turned out crashing my program upon start up (note, the example program calculator is working fine before modification).. i modified the following code snippet: (:layouts (default (with-slots (text-field) *application-frame* (vertically (:width 150 :max-width 500) (setf text-field screen) (horizontally (:height 50) ac ce) (tabling (:grid t) (list one two three four) (list five six seven eight) (list nine zero plus dash) (list multiply divide result)))))) (:top-level (calculator-frame-top-level . nil))) the fifth last line to second last line would be the lines of interest.. i just modified some layout component (or i thought to be), and it gave me the following error: There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION CLIM:MOVE-SHEET (2)> when called with arguments (NIL 69 99). [Condition of type SIMPLE-ERROR] Backtrace: 0: ((SB-PCL::FAST-METHOD NO-APPLICABLE-METHOD (T)) #<unavailable argument> #<unavailable argument> #<STANDARD-GENERIC-FUNCTION CLIM:MOVE-SHEET (2)> (NIL 69 99)) 1: ((SB-PCL::FAST-METHOD NO-APPLICABLE-METHOD (T)) #<unavailable argument> #<unavailable argument> #<STANDARD-GENERIC-FUNCTION CLIM:MOVE-SHEET (2)> (NIL 69 99)) 2: ((SB-PCL::FAST-METHOD CLIM:ALLOCATE-SPACE (CLIM:GRID-PANE T T)) (#(NIL 37) . #()) #<unavailable argument> #<CLIM:GRID-PANE "(Unnamed Pane)" {9D40E49}> 92 132) 3: ((SB-PCL::FAST-METHOD CLIM-INTERNALS::BOX-LAYOUT-MIXIN/VERTICALLY-ALLOCATE-SPACE (CLIM-INTERNALS::BOX-LAYOUT-MIXIN T T)) (#(NIL 32) . #()) #<unavailable argument> #<CLIM:VRACK-PANE "(Unnamed Pane)" {9D49159}> 92 186) 4: ((SB-PCL::FAST-METHOD CLIM-INTERNALS::BOX-LAYOUT-MIXIN/VERTICALLY-ALLOCATE-SPACE (CLIM-INTERNALS::BOX-LAYOUT-MIXIN T T)) (#(NIL 32) . #()) #<unavailable argument> #<CLIM:VRACK-PANE "(Unnamed Pane)" {9D50D69}> 92 190) 5: ((LAMBDA (SB-PCL::.PV-CELL. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0. SB-PCL::.ARG1. SB-PCL::.ARG2.)) #<unavailable argument> #<unavailable argument> #<CLIM-INTERNALS::TOP-LEVEL-SHEET-PANE CLIM-INTERNALS::TOP-LEVEL-SHEET {A305B91}> 92 190) 6: ((LAMBDA (SB-PCL::.PV-CELL. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0. SB-PCL::.ARG1.)) #<unavailable argument> #<unavailable argument> #<CLIM-CLX::CLX-FRAME-MANAGER {9A226E9}> #<CLIM-DEMO::CALCULATOR {A35C971}>) 7: ((SB-PCL::FAST-METHOD CLIM:ADOPT-FRAME (CLIM:FRAME-MANAGER CLIM:APPLICATION-FRAME)) (#(NIL 1 15 12) . #()) #<unavailable argument> #<CLIM-CLX::CLX-FRAME-MANAGER {9A226E9}> #<CLIM-DEMO::CALCULATOR {A35C971}>) 8: ((LAMBDA (SB-PCL::.PV-CELL. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0. SB-PCL::.ARG1.)) #<unavailable argument> #<unavailable argument> #<CLIM-CLX::CLX-FRAME-MANAGER {9A226E9}> #<CLIM-DEMO::CALCULATOR {A35C971}>) 9: ((SB-PCL::FAST-METHOD CLIM:RUN-FRAME-TOP-LEVEL :AROUND (CLIM:APPLICATION-FRAME)) #<unavailable argument> #S(SB-PCL::FAST-METHOD-CALL :FUNCTION #<FUNCTION (SB-PCL::FAST-METHOD CLIM:RUN-FRAME-TOP-LEVEL #)> :PV-CELL NIL :NEXT-METHOD-CALL NIL :ARG-INFO (1 . T)) #<CLIM-DEMO::CALCULATOR {A35C971}> NIL) 10: (CLIM-DEMO::CALCULATOR) 11: (SB-INT:EVAL-IN-LEXENV (CLIM-DEMO::CALCULATOR) #<NULL-LEXENV>) 12: (SWANK::EVAL-REGION "(clim-demo::calculator) " T) 13: ((LAMBDA NIL)) 14: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-SYNTAX-HOOKS (T)) #<unused argument> #<unused argument> #<CLOSURE (LAMBDA NIL) {A35C0B5}>) 15: (SWANK:LISTENER-EVAL "(clim-demo::calculator) ") 16: (SB-INT:EVAL-IN-LEXENV (SWANK:LISTENER-EVAL "(clim-demo::calculator) ") #<NULL-LEXENV>) 17: ((LAMBDA NIL)) 18: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK (T T)) #<unused argument> #<unused argument> #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA NIL) {A35BF25}>) 19: ((LAMBDA NIL)) 20: (SWANK::CALL-WITH-REDIRECTED-IO #<SWANK::CONNECTION {A4ACDA1}> #<FUNCTION (LAMBDA NIL) {B45C885}>) 21: (SWANK::HANDLE-REQUEST #<SWANK::CONNECTION {A4ACDA1}>) 22: ((LAMBDA NIL)) 23: ((LAMBDA NIL)) 24: (SWANK::CALL-WITH-REDIRECTED-IO #<SWANK::CONNECTION {A4ACDA1}> #<CLOSURE (LAMBDA NIL) {9070075}>) 25: (SWANK::REPL-LOOP #<SWANK::CONNECTION {A4ACDA1}>) 26: (SWANK::CALL-WITH-BINDINGS NIL #<CLOSURE (LAMBDA NIL) {9070055}>) 27: ((LAMBDA NIL)) 28: ("foreign function: call_into_lisp") 29: ("foreign function: funcall0") anyone know what's wrong? thanks alot :D -- www.programer.name - my own personal blog : )

1 0

[mcclim-devel] question about format-graph-from-roots
by rpgoldman＠real-time.com 13 Apr '05

13 Apr '05

One suggested patch and one question: 1. Suggested patch: should we modify format-graph-from roots so that the defualt value for :arc-drawer is #'clim-internals::standard-arc-drawer? 2. I have been trying to figure out how to draw a graph that has multiple different kinds of edges. Actually, more specifically, I would like to draw a graph that is "mostly" a tree: it has a tree backbone, and then has some cross-edges. It isn't at all obvious how to do this nicely. There are (at least) two problems: i. I don't see an elegant way to indicate the type of edges. AFAICT, the CLIM spec indicates that we simply generate children, i.e., nodes. We never generate edges, except implicitly. My best guess is that the way to do this is either: a. have the "from" node always have enough information to determine what sort of edge is to be drawn from it to the "to" node. This actually breaks down a little in the case where there can be multiple arcs from one "from" to a single "to." b. create a new data structure (some form of association like a hash table, alist or whatever) that records the type of arc to be drawn, and stuff it into your arc drawer function. ii. More seriously, there doesn't seem any obvious way to say that an arc between "from" and "to" is a cross-edge, and shouldn't increment the depth of "to," rather than being a child edge that DOES increment the depth. Anyone have any suggestions for this? It seems the more difficult problem. Best, R

3 4

[mcclim-devel] typesetting CLIM spec
by rpgoldman＠real-time.com 12 Apr '05

12 Apr '05

Flushed with my success pdf-ulating the manual, I had a run up at the CLIM spec. This seems to work with minimal patching. Simply apply the following, and use pdflatex instead of latex, and you get a version that has bookmarks and hyperlinks in it. One problem: regions.tex seems to require a file named file-normalization.epsi. I was going to translate it into pdf, but found that it's nowhere in the copy of mcclim that I checked out. Is this a bug with the spec LaTex? Best, r Index: clim.tex =================================================================== RCS file: /project/mcclim/cvsroot/mcclim/Spec/src/clim.tex,v retrieving revision 1.1 diff -c -r1.1 clim.tex *** clim.tex 11 Dec 2000 06:59:59 -0000 1.1 --- clim.tex 12 Apr 2005 18:54:56 -0000 *************** *** 17,22 **** --- 17,29 ---- {\end{small}\clearpage} \makeatother + %% added to try to make nice bookmarks in PDF... [2005/04/12:rpg] + \ifx\pdfoutput\undefined \csname newcount\endcsname\pdfoutput \fi + \ifcase\pdfoutput \else + \usepackage[pdftex]{hyperref} + \fi + + %\usepackage{times} %% For PDF

1 0

[mcclim-devel] fussy clean-up items
by rpgoldman＠sift.info 07 Apr '05

07 Apr '05

I was just reading over the warnings the ACL compiler gives me, and I noticed that we have three definitions of make-keyword, in presentations.lisp, commands.lisp, and utils.lisp. I don't claim to understand the dueling system definitions (mk-defsystem and asdf) to know which ones should be killed, but any objections to killing a couple? Also, the compiler beefs about double definitions of (METHOD %PRESENTATION-TYPEP (T T T)) and (METHOD %PRESENT (T T T T TEXTUAL-VIEW)) is this due to the eval-when form being evaluated first at compile time, and then at load time? Cheers, r

1 0