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

Issue Loading McClim
by Oscar Chappel 29 May '20

29 May '20

Hello, I am just starting to work with Common Lisp user interface development tools. I’m running SBCL, SLIME, in EMACS on a Mac using High Sierra 10.13.6. I’m trying to use quicklisp to load McClim. When I execute (ql:quickload :mcclim) I get the following error: Circular dependency: ((#<ASDF/FIND-SYSTEM:DEFINE-OP > . #<ASDF/SYSTEM:SYSTEM "esa-mcclim">)) [Condition of type ASDF/ACTION:CIRCULAR-DEPENDENCY] Here is the stack trace: Backtrace: 0: ((LAMBDA NIL :IN ASDF/ACTION:CALL-WHILE-VISITING-ACTION)) 1: (ASDF/PLAN:TRAVERSE-ACTION #<ASDF/PLAN:SEQUENTIAL-PLAN {10067B53D3}> #<ASDF/FIND-SYSTEM:DEFINE-OP > #<ASDF/SYSTEM:SYSTEM "esa-mcclim"> T) 2: ((LAMBDA NIL :IN ASDF/PLAN:MAKE-PLAN)) 3: ((:METHOD ASDF/OPERATE:OPERATE (ASDF/OPERATION:OPERATION ASDF/COMPONENT:COMPONENT)) #<ASDF/FIND-SYSTEM:DEFINE-OP > #<ASDF/SYSTEM:SYSTEM "esa-mcclim"> :PLAN-CLASS NIL :PLAN-OPTIONS NIL) [fast-method] 4: ((SB-PCL::EMF ASDF/OPERATE:OPERATE) #<unused argument> #<unused argument> #<ASDF/FIND-SYSTEM:DEFINE-OP > #<ASDF/SYSTEM:SYSTEM "esa-mcclim">) 5: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE)) 6: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) #<ASDF/FIND-SYSTEM:DEFINE-OP > #<ASDF/SYSTEM:SYSTEM "esa-mcclim">) [fast-method] 7: ((LAMBDA NIL :IN ASDF/SYSTEM:FIND-SYSTEM)) 8: (ASDF/SESSION:CONSULT-ASDF-CACHE (ASDF/SYSTEM:FIND-SYSTEM "esa-mcclim") #<CLOSURE (LAMBDA NIL :IN ASDF/SYSTEM:FIND-SYSTEM) {10067B372B}>) 9: ((:METHOD ASDF/ACTION:PERFORM :AROUND (T T)) #<ASDF/FIND-SYSTEM:DEFINE-OP > #<ASDF/SYSTEM:SYSTEM "esa-mcclim">) [fast-method] 10: ((LAMBDA NIL :IN ASDF/ACTION:CALL-WHILE-VISITING-ACTION)) 11: ((:METHOD ASDF/ACTION:PERFORM-WITH-RESTARTS :AROUND (T T)) #<ASDF/FIND-SYSTEM:DEFINE-OP > #<ASDF/SYSTEM:SYSTEM "esa-mcclim">) [fast-method] 12: ((:METHOD ASDF/PLAN:PERFORM-PLAN (T)) #<ASDF/PLAN:SEQUENTIAL-PLAN {10067B26B3}>) [fast-method] 13: ((FLET SB-C::WITH-IT :IN SB-C::%WITH-COMPILATION-UNIT)) 14: ((:METHOD ASDF/PLAN:PERFORM-PLAN :AROUND (T)) #<ASDF/PLAN:SEQUENTIAL-PLAN {10067B26B3}>) [fast-method] 15: ((:METHOD ASDF/OPERATE:OPERATE (ASDF/OPERATION:OPERATION ASDF/COMPONENT:COMPONENT)) #<ASDF/FIND-SYSTEM:DEFINE-OP > #<ASDF/SYSTEM:SYSTEM "esa-mcclim"> :PLAN-CLASS NIL :PLAN-OPTIONS NIL) [fast-method] 16: ((SB-PCL::EMF ASDF/OPERATE:OPERATE) #<unused argument> #<unused argument> #<ASDF/FIND-SYSTEM:DEFINE-OP > #<ASDF/SYSTEM:SYSTEM "esa-mcclim">) 17: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE)) 18: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) #<ASDF/FIND-SYSTEM:DEFINE-OP > #<ASDF/SYSTEM:SYSTEM "esa-mcclim">) [fast-method] 19: ((LAMBDA NIL :IN ASDF/SYSTEM:FIND-SYSTEM)) Can anyone point me to a solution? Thanks. Sincerely, Oscar Chappel

2 1

CL IDE development setup?
by Harsh Raju Chamarthi 29 Apr '20

29 Apr '20

Hello McCLIM developers, Is anybody actively working on a McCLIM based Common Lisp IDE? I was wondering if there is a pointer for how to setup the development environment.. Thanks.

3 2

Some sparse questions
by Andrea De Michele 19 Jan '20

19 Jan '20

Dear all, I'm working on CLIM-PDF backend and I solved some problems like the text direction in landscape orientation, but I don't like the solution so I didn't submit any PR. Instead I write here to have some feedback from you about some issues that I have found, some very PDF specific other in the very core of McCLIM. I'm start from the more pdf specific (and easier) to the more general one (and harder): 1) WITH-OUTPUT-TO-PDF-STREAM macro: The PDF backend is used through WITH-OUTPUT-TO-PDF-STREAM that is based on the analogous macro for Postscript backend defined in the Spec. I think it is better to define for PDF backend a WITH-OUTPUT-TO-PDF-FILE with a string or a pathname as argument instead of a stream. In this way the user don't have to open the file stream (the user needs also to known that the stream must be open with keyword :element-type '(unsigned-byte 8)). If we remove the WITH-OUTPUT-TO-PDF-STREAM McCLIM can remove the dependency to FLEXI-STREM system. The difference from PDF to Postscript is giustified because PDF is a file format so the output is ever a file, instead the Postscript output can be send on a stream directly atttached to a postscript printer. We can also add a WITH-OUTPUT-TO-POSTSCRIPT-FILE macro without remove the WITH-OUTPUT-TO-POSTSCRIPT-STREAM defined in the Specification. 2) GRAFT in PDF and Postscript Backend PDF and Postscript Backend define their GRAFT but then never use it. The stream sheet where the output is drawn is not a child of a graft. I think this is not correct. 3) GRAFT in general Now each backend define its GRAFT. I think that the backend could only initialize a standard-graft with the right information (in MAKE-GRAFT generic) like: mirror, width, height, device-millimiter-density, backend-transformation, and leave all the other stuff in the common graft module "Core/clim-basic/windowing/grafts.lisp" 4) transformation and region machinery Is it the transformation and region machinery correct? Or it is works only in some standard situaions? For example I think that we could obtain a Zoom effect simply by: (setf (sheet-transformation some-sheet) (make-scaling-transformation 1.5 1.5)) but this doesn't work on McCLIM (I try it in the listener demo of clim-tos and there it works). Follow some more specific topics: 4a) Setting sheet-native-transformation: McCLIM set directly the SHEET-NATIVE-TRANSFORMATION with %%SET-SHEET-NATIVE-TRANSFORMATION. I think this is not correct the sheet-native-transformation must be computated and only cached never set directly, otherwise you can lost the parent trasformation. 4b) sheet-native-transformation for basic-sheet: (defmethod sheet-native-transformation ((sheet basic-sheet)) (with-slots (native-transformation) sheet (unless native-transformation (setf native-transformation (if-let ((parent (sheet-parent sheet))) (compose-transformations (sheet-native-transformation parent) (sheet-transformation sheet)) +identity-transformation+))) native-transformation)) it's not correct because didn't take in account the mirror transformation if the mirror of sheet it is not the same of the parent. So we need to correct this or to add a method for mirrored-sheet-mixin. Of course we didn't see the error because often McCLIM set directly sheet-native-transform as written before in 4a) 4c) What is sheet-native-region? >From the spec: "Returns the region for the sheet sheet in native coordinates". This is not clear. The first time that I read it I understood that it is the sheet-region of the sheet transformed in native coordinates, that means for examples that a sheet with a region +everywhere+ have a native-region +everywhere+. Instead for McCLIM, and clim-tos too, it is the region of the mirror "for" the sheet i.e. the sheet-region of the sheet transformed in native coordinates clipped by the mirror region. This interpretation maybe is correct because the spec said about sheet-device-region: "Returns the actual clipping region to be used when drawing on the mirror. This is the intersection of the user's clipping region (transformed by the device transformation) with the sheet's native region." Anyway, in this case, the sheet-native-region for the graft in Mcclim is wrong: it is +everywhere+ -- Andrea De Michele

3 6

stuck over accepting values ..
by gwbennett 16 Jan '20

16 Jan '20

Hello from Greg Bennett running sbcl-1.5.8 inside emacs, and using mcclim-20181227-git. TASK: I am trying, unsuccessfully at the moment, to use accepting values, in an environment which I need to define, to receive something and then make it available for subsequent action. I assume that this must be possible so that applications can receive such input. In mccli ...-git/Examples/accepting-values.lisp I found the defun for accepting-tag which seemed a perfect model. It runs, of course, inside the :clim-demo package as part of the huge menu of (demodemo). It will not run outside that environment, and as Daniel Kochmanski kindly explained to me, the reason centres on the nature of the stream *query-io*. As Daniel suggested, things run correctly (outside) if I fire up a clim-listener and use that as my interface to the code. (My other negotiations with clim-listener have been less successful.) For the project I am working on porting I should like to be able accomplish TASK. I have read pieces of the CLIM 2 User Guide (version 2.2.2) in the hope of finding some information that would help, but my aging brain locks up in the face of its long sequence of definitions and code snippets. However, on p196-7 Section 9.5.1 of that manual there is an example (good!) which looks like a version of accepting-tag; it's code is attached as p196.lsp. When I try to execute it, I immediately run into what I take to be related to the *query-io* difficulty with the error: There is no class named COMMON-LISP:NIL. [Condition of type SB-PCL:CLASS-NOT-FOUND-ERROR] Some top pieces of the backtrace are attached in p196-log.lsp in case they are helpful. I should be very grateful for pointers to things I have evidently missed and/or failed to understand in my attempts to collect input on the fly. Cheers /Greg Bennett

2 1

QTools as a cross-platform backend?
by mike thomas 07 Jan '20

07 Jan '20

Hi there I'm not a member of this list - couldn't find how to subscribe - so apologies for directly sending. I just have two questions: Has consideration been given to basing a back-end on QTools? Does it have potential to do the job, or is it better to work directly through native OS capabilities. Cheers Mike Thomas

4 4

clim-utils again
by gwbennett 15 Dec '19

15 Dec '19

Good day from Greg Bennett who is running sbcl-1.5.8 under linux mint 19.2 64-bit and mcclim code from mcclim-20191008-get via quicklisp. I would like to learn more about the coordinate system behind the &key arguments left top right bottom in the call to make-application-frame. This seems to be a coordinate system for a device which defaults to the full size of the root window, whatever that is. As far as I can tell (some) details might be in the package clim-utils but this does not seem to be part of the mcclim I am using. Pointers to its definition and to the device coordinate system would be much appreciated. Cheers /Greg

2 1

Running the examples
by gwbennett 15 Dec '19

15 Dec '19

Good day from Greg Bennett who is running sbcl-1.5.8 in emacs under linux mint 19.2 64-bit and mcclim code from mcclim-20191008-get via quicklisp. I am trying to understand some of the mcclim examples which use accepting-values. In my case the code is in ...../mcclim-20191008-git/Examples/accepting-values.lisp At the top of this file there is this note: ;;; Some simple examples from the Franz user manual. You can run ;;; these from the listener. Thus encouraged, I tried some of these after loading the demo asdf. For example, I tried to use (defun accept-popup (seq &key (stream *query-io*)) (let ((val (elt seq 0)) (ptype `(completion ,seq))) (accepting-values (stream) (setq val (accept ptype :stream stream :view climi::+pop-up-menu-view+ :prompt "Choose one:" :default val))) val)) ;; via (accept-popup (list 3 5 7 9)) In every instance I fail with: There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION CLIM:STREAM-CURSOR-POSITION (2)> when called with arguments (#<SYNONYM-STREAM :SYMBOL SWANK::*CURRENT-QUERY-IO* {10016D0A93}>). [Condition of type SB-PCL::NO-APPLICABLE-METHOD-ERROR] which, I think, means that my difficulty lies in the interface between emacs (swank) and the form I'm experimenting with, even 'though that code runs perfectly when invoked in (demodemo). In particular, the invocation of *query-io* (which evaluates to the #<SYNONYM-STREAM :SYMBOL SWANK::*CURRENT-QUERY-IO* {10016D0A93}> of the error is evidently something which I am getting wrong. I should be grateful to learn how be able to run the elements of (demodemo) from a listener (connected to lisp via emacs) Cheers /Greg

2 1

package clim-utils
by gwbennett 01 Dec '19

01 Dec '19

Good day from Greg Bennett who is running sbcl-1.5.8 under linux mint 19.2 64-bit and mcclim code from mcclim-20191008-get via quicklisp. I would like to learn more about the coordinate system behind the &key arguments left top right bottom in the call to make-application-frame. This seems to be a coordinate system for a device which defaults to the full size of the root window, whatever that is. As far as I can tell (some) details might be in the package clim-utils but this does not seem to be part of the mcclim I am using. Pointers to its definition and to the device coordinate system would be much appreciated. Cheers /Greg

1 0

Displaying updated menubars
by Greg Bennett 21 Oct '19

21 Oct '19

From Greg Bennett running sbcl1.5.0 under linux mint 18.3, and for whom releases.txt in quicklisp shows mcclim-20191008. Using menutest.lisp in Examples in that release, I have been trying to display and use an additional command in an existing, running menubar by updating the appropriate command table. While updating the command table works, I cannot get the display to use the new table short of destroying the frame and rebuilding the appropriate command table and frame. I see in https://github.com/McCLIM/McCLIM/issues/21 a discussion which tells me that the solution is complicated but exists. The discussion ends with Fix menu bar #153 Merged dkochmanski closed thi in b7c6ce9 on Apr 9, 2017 This suggests that the solution is part of mcclim but that I have not yet found it. The discussion is significantly above my lisp pay-grade, I'm afraid, so before I go about stomping on things in an attempt to implement a solution ... Could someone please point me to the details so that I can (try to) understand the solution ? If I'm incorrect in assuming that the solution is part of mcclim, could someone tell me how to make the solution part of my mcclim ? Cheers /Greg Bennett

1 0

Re: Trying to use McCLIM
by Craig Lanning 19 Oct '19

19 Oct '19

See below. On Sat, 2019-10-19 at 14:06 -0400, Craig Lanning wrote: > On Sat, 2019-10-19 at 18:28 +0200, Daniel Kochmański wrote: > > Hey, > > > > Craig Lanning writes: > > > Have you figured anything out about this issue? > > > > > > > I think that reply from last Saturday on the mailing list from > > Andrea > > explains the issue: > > I'm not on the mailling list so if it wasn't sent directly to me. I > didn't see it. > > > > I tried your code to see why the commands are disabled. I think > > > this is > > > due to the fact that the commands are not inserted in the command > > > table: > > That is interesting since LispWorks and Symbolics don't expect the > commands to be in the table. I think they add them to the table since > they show up in the menu. I'll check in LispWorks to see if directly > adding them to the table causes any problems. I end up having to define the command-table, then define the commands (adding them to the appropriate tables), then add menu items to each command table for the appropriate commands. I think that for this reason Symbolics and LispWorks each have the command table automatically add commands that show up in the command table. This way you only need to define the commands and the command table. You don't have to run any other functions to get your command- tables to have the correct menu and command entries. I think that the original CLIM intent was that the user would only have to define the commands and the command-table and do nothing else. Once I got the app working with McCLIM, I noticed that sometimes when I click on another class to change what is being displayed, it doesn't properly update the display panes. > > > -------- > > > CB> (command-present-in-command-table-p 'com-show-info 'cb-file) > > > NIL > > > -------- > > > Evidently Symbolics and Franz versions of macro define-command- > > > table > > > automatically add the commands in :menu argument to the command- > > > table, > > > mcclim version no. > > > So you need to add by hand the commands to command-table like > > > that: > > > --------- > > > (add-command-to-command-table 'com-show-info 'cb-file) > > > --------- > > > or use the :command-table name option in define command (for this > > > you > > > need to define the command-table before the command): > > This is interesting since I have to define the table after the > commands > for them to be picked up due to the menu. > > > > ----------- > > > (define-command (com-show-info :command-table cb-file) () > > > ... > > > ...) > > > ----------------- > > > > Jan also had few remarks on IRC (partially overlapping with the > > above): > > > > > jackdaniel if anyone feels like debugging why commands are > > > disabled > > > in a definition which looks fine at the first glance please take > > > a > > > look at > > > https://mailman.common-lisp.net/pipermail/mcclim-devel/2019-October/002129.… > > > scymtym jackdaniel: the commands don't seem to be defined within > > > any command table. adding e.g. :command-table cb-file enables the > > > menu entries > > > scymtym i haven't seen commands defined like that before > > > scymtym the spec says without :command-table, the command will > > > not > > > be added to any command table. i would assume that makes the > > > command not accessible in the menu command table > > > scymtym this example programs assumes CLASS is a builtin > > > presentation type and CLASS-NAME can be applied to slots > > > scymtym it's pretty weird > > I found a few issues with my code after I sent it. After I fixed the > issues I sent a newer version of my code to both Daniel and the list. > > Craig > > > Best regards, > > Daniel > > > > -- > > Daniel Kochmański ;; aka jackdaniel | Przemyśl, Poland > > TurtleWare - Daniel Kochmański | www.turtleware.eu > > > > "Be the change that you wish to see in the world." - Mahatma Gandhi

1 0