mcclim-devel

mcclim-devel@common-lisp.net

820 discussions

McCLIM, 1.2.8 An application displaying a data structure
by igor denisov 11 Nov '20

11 Nov '20

(in-package :common-lisp-user) (defpackage "APP" (:use :clim :clim-lisp) (:export "APP-MAIN")) (define-application-frame superapp () ( ;(current-number :initform nil ;:accessor current-number) ) (:pointer-documentation t) (:panes (app :application :display-time nil :height 400 :width 600) (int :interactor :height 200 :width 600)) (:layouts (default (vertically () app int)))) ; Evaluation aborted on #<UNBOUND-VARIABLE SUPERAPP {100A25ABA3}>. How this can be or I missed something again. The variable SUPERAPP is unbound. [Condition of type UNBOUND-VARIABLE] best, Igor.

1 0

CLIM Title Pane
by Oscar Chappel 05 Oct '20

05 Oct '20

I’m experimenting with McClim and CLIM. Right now, I’m trying to insert a title pane into an application frame. I’m using the “Mini-CAD” example in figure 20 of the CommonLisp Interface Manager 2.0 User's Guide - 30 Jul 2004 When I use the :display-string initialization argument for the title pane, I get an error: “Invalid initialization argument :DISPLAY-STRING in call for class #<STANDARD-CLASS CLIM-CLX::CLX-1255-TITLE-PANE>.” I have found that using the :display-function results in a similar error. Can anyone help out with this? Thanks, Oscar Chappel

3 2

Issue Loading McClim
by Oscar Chappel 10 Aug '20

10 Aug '20

Good morning, I’m having an issue loading McClim on my MacBook Pro. I’m running Mac OS Catalina version 10.15.6, Emacs version 23.6 with slime and SBCL. I have quicklisp installed. When I execute (ql:quickload :mcclim) the process starts and then I get the error “No symbol named *STANDARD-OPTIMIZED-SETTINGS* in CL-PPCRE. Can anyone tell me what I’m missing? Thanks, Oscar Chappel

3 2

climguide of lispworks reliable? (function "bordering" is not defined)
by oleg harput 12 Jul '20

12 Jul '20

(clim:define-application-frame test () ((height :initform 55 :accessor height)) (:panes (main :application :display-function 'display-main) (promper :interactor)) (:layouts (:default (clim:vertically () (2/3 (bordering () main));;;;<=??? (1/3 promper))))) why?

1 0

Can i use CLIM 2 User Guide by Franz Inc. in SBCL(with mcclim)?
by oleg harput 12 Jul '20

12 Jul '20

Can i use CLIM 2 User Guide by Franz Inc. in SBCL(with mcclim)? the example (defun test () (flet ((run () (let ((frame (make-application-frame 'test))) (setq *test-frame* frame) (run-frame-top-level frame)))) (mp:process-run-function "test" #'run))) does not work because of the (mp:process-run-function "test" #'run) term . What does mean mp:?

2 1

Re: Issue Loading McClim
by Oscar Chappel 31 May '20

31 May '20

Hi Nisar, I did what you recommended, it halted initially and quicklisp gave me a warning that it couldn’t load from the directory that I deleted so I selected the option to reconfigure and retry, that worked. I got one additional warning regarding a need to manually configure what I believe to be a font. Other than that, all went well. Now I’ll try doing some actual development with McClim. Thank You. Oscar

1 0

Re: Issue Loading McClim
by Oscar Chappel 31 May '20

31 May '20

Hi Nisar, Here is the list of information you requested: (list (asdf:asdf-version) (lisp-implementation-version) (ql:dist-version "quicklisp") (ql:where-is-system :mcclim)) ("3.3.1" "2.0.4" "2020-04-27" #P"/Users/oscarchappel/common-lisp/mcclim-0.9.6/“) Thanks, Oscar

2 1

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

← Newer
1
2
3
4
5
6
7
...
82
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

mcclim-devel