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

[mcclim-devel] read-gesture again
by Robert Strandh 31 Dec '04

31 Dec '04

Hello again, >From comments in stream-read-gesture, I get the impression that :peek-p is not working currently. -- Robert Strandh --------------------------------------------------------------------- Greenspun's Tenth Rule of Programming: any sufficiently complicated C or Fortran program contains an ad hoc informally-specified bug-ridden slow implementation of half of Common Lisp. ---------------------------------------------------------------------

1 0

[mcclim-devel] stream-unread-gesture possible bug
by Robert Strandh 31 Dec '04

31 Dec '04

Hello, I suspect stream-unread-gesture does not work. When stream-read-gesture returns a character and that character gets put back in the stream, it looks like event-sheet gets called on the character (perhaps when it is read again). Obviously, event-sheet does not have a method on characters. -- Robert Strandh --------------------------------------------------------------------- Greenspun's Tenth Rule of Programming: any sufficiently complicated C or Fortran program contains an ad hoc informally-specified bug-ridden slow implementation of half of Common Lisp. ---------------------------------------------------------------------

1 0

[mcclim-devel] Springtail 0.0 released
by Milan Zamazal 30 Dec '04

30 Dec '04

Springtail 0.0 released ======================= This is the first release of my McCLIM based Common Lisp digital photo collection manager. A simple McCLIM off-line Wikipedia client and a very simple CLX based digital clock able to crash SBCL are also included. Please note this is a tentative release. While I use Springtail regularly and it works quite well for me, it is highly personalized and I don't think it can be used by anyone else out of the box, if at all, in its current state. So why am I releasing it? - I'd like to provide an example of actual use of the McCLIM's image extensions. - I'd like to contribute another example code of a non-trivial McCLIM application, to support McCLIM use and further development. - Well, when it has been already written: Maybe someone else could find a McCLIM based digital photo manager useful. I'm not sure, so I ask about it this way. You can download Springtail 0.0 from http://www.zamazal.org/software/springtail/download/springtail-0.0.tar.gz

2 1

[mcclim-devel] missing doc page
by Paul Werkowski 29 Dec '04

29 Dec '04

The table of contents page of the CLIM spec is a dead link http://www.stud.uni-karlsuhe.de/~unk6/clim-spec/NIL gets a http 404 file not found error. Paul

4 5

[mcclim-devel] How to resize a pane with scrollbars?
by Daniel Barlow 29 Dec '04

29 Dec '04

In the barebones clim app below, using the "Resize Input" command to resize the interactor pane causes the scrollbar thumb to resize so that the new bigger interactor can be scrolled around. This is what I'd expect. Resizing the application pane in similar fashion ("Resize Output") however, has no effect that I can see. I've only been using clim for a few days, so it's not obvious to me that it's supposed to work like this anyway. If it isn't, please feel free to say so. How should I be doing this? (The name of this application is because I initially suspected from TRACEing COMPOSE-SPACE that there was a vrack pane swallowing the space requirement and substituting its own. Now, though, I just believe I don't understand the layout protocol anyway) (clim:define-application-frame vrack-test () () (:pointer-documentation t) (:panes (track :application :scroll-bars :vertical ;:width 600 :height 400 ) (int :interactor :height 120 :width 600)) (:layouts (default (vertically () track int)))) (define-vrack-test-command (com-quit :name "Quit") () (frame-exit *application-frame*)) (define-vrack-test-command (com-resize-out :name "Resize Output") ((size 'number)) (change-space-requirements *standard-output* :width 600 :height size)) (define-vrack-test-command (com-resize-in :name "Resize Input") ((size 'number)) (change-space-requirements *standard-input* :width 600 :height size))) (run-frame-top-level (make-application-frame 'vrack-test)) -- "please make sure that the person is your friend before you confirm"

2 1

[mcclim-devel] question about display functions and control apps
by rpgoldman＠real-time.com 29 Dec '04

29 Dec '04

The examples I have seen of display functions and McCLIM, it seems like there are two dominant models: one where the user does some commands, and the application pane's display function stays in synch by updating at every command loop (I suppose this is the MVC model); and another where we write code in the commands that directly display stuff (and have to tell the application pane NOT to redisplay itself). Question: what about the case where you want to watch something "out there" that is not under the control of the command loop. I'm thinking in particular about controls applications, where you might want to update a display that shows the current state of the plant. Typically, there will be some process sampling the world at some rate, and wanting to asynchronously update the state display. Has anyone built an application like that using CLIM? Any suggestions for the right model? Thanks! R

4 5

[mcclim-devel] Application pane vertical scrolling does not work with table formatting
by Paolo Amoroso 29 Dec '04

29 Dec '04

I have found an annoying problem that severely limits the use of table formatting in application panes. This sample code shows the problem: (in-package :clim-user) (define-application-frame no-scroll () () (:pointer-documentation t) (:panes (app :application :display-time :command-loop :display-function 'display-function :end-of-line-action :wrap :end-of-page-action :scroll :scroll-bars t)) (:layouts (default app))) (defun display-function (frame stream) (declare (ignore frame)) (formatting-table (stream) (dotimes (i 100) (formatting-row (stream) (formatting-cell (stream) (princ i)))))) (define-no-scroll-command (com-quit :menu t) () (frame-exit *application-frame*)) Run it with: (run-frame-top-level (make-application-frame 'no-scroll)) Although the tabular output is longer than the application pane's viewport, it is not possible to vertically scroll it to see the remaining part. The thumb occupies all the scroll bar's area, as if there was no additional output. Is the above code supposed to work? Am I doing anything wrong? Any workarounds? Paolo -- Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film

4 4

[mcclim-devel] Fix for Scigraph package lock error with CMUCL
by Robert Strandh 28 Dec '04

28 Dec '04

Paolo Amoroso writes: > The current CVS sources of Scigraph generate a package lock error > during compilation or load with recent versions of CMUCL, I think the > 19a prerelease and release series. It is caused by a conflict with > the symbol `cl:variable'. The problem can be fixed by changing in > file Apps/Scigraph/scigraph/package.lisp the form: > > (eval-when (compile load eval) > (defpackage GRAPH > #-allegro (:nicknames gr) ; "GR" names something already. > #+allegro (:shadow variable) ; shouldn't be inherited but is > #+MCL (:shadow copy) > (:use dwim-lisp tool statistics))) > > to this, which removes the conditionalization of `variable' shadowing > for allegro: > > (eval-when (compile load eval) > (defpackage GRAPH > #-allegro (:nicknames gr) ; "GR" names something already. > (:shadow variable) ; shouldn't be inherited but is > #+MCL (:shadow copy) > (:use dwim-lisp tool statistics))) Patch applied. Thanks. -- Robert Strandh --------------------------------------------------------------------- Greenspun's Tenth Rule of Programming: any sufficiently complicated C or Fortran program contains an ad hoc informally-specified bug-ridden slow implementation of half of Common Lisp. ---------------------------------------------------------------------

1 0

[mcclim-devel] Fix for Scigraph package lock error with CMUCL
by Robert Strandh 28 Dec '04

28 Dec '04

Paolo Amoroso writes: > The current CVS sources of Scigraph generate a package lock error > during compilation or load with recent versions of CMUCL, I think the > 19a prerelease and release series. It is caused by a conflict with > the symbol `cl:variable'. The problem can be fixed by changing in > file Apps/Scigraph/scigraph/package.lisp the form: > > (eval-when (compile load eval) > (defpackage GRAPH > #-allegro (:nicknames gr) ; "GR" names something already. > #+allegro (:shadow variable) ; shouldn't be inherited but is > #+MCL (:shadow copy) > (:use dwim-lisp tool statistics))) > > to this, which removes the conditionalization of `variable' shadowing > for allegro: > > (eval-when (compile load eval) > (defpackage GRAPH > #-allegro (:nicknames gr) ; "GR" names something already. > (:shadow variable) ; shouldn't be inherited but is > #+MCL (:shadow copy) > (:use dwim-lisp tool statistics))) Patch applied. Thanks. -- Robert Strandh --------------------------------------------------------------------- Greenspun's Tenth Rule of Programming: any sufficiently complicated C or Fortran program contains an ad hoc informally-specified bug-ridden slow implementation of half of Common Lisp. ---------------------------------------------------------------------

1 0

[mcclim-devel] Fix for Scigraph package lock error with CMUCL
by Robert Strandh 28 Dec '04

28 Dec '04

Paolo Amoroso writes: > The current CVS sources of Scigraph generate a package lock error > during compilation or load with recent versions of CMUCL, I think the > 19a prerelease and release series. It is caused by a conflict with > the symbol `cl:variable'. The problem can be fixed by changing in > file Apps/Scigraph/scigraph/package.lisp the form: > > (eval-when (compile load eval) > (defpackage GRAPH > #-allegro (:nicknames gr) ; "GR" names something already. > #+allegro (:shadow variable) ; shouldn't be inherited but is > #+MCL (:shadow copy) > (:use dwim-lisp tool statistics))) > > to this, which removes the conditionalization of `variable' shadowing > for allegro: > > (eval-when (compile load eval) > (defpackage GRAPH > #-allegro (:nicknames gr) ; "GR" names something already. > (:shadow variable) ; shouldn't be inherited but is > #+MCL (:shadow copy) > (:use dwim-lisp tool statistics))) Patch applied. Thanks. -- Robert Strandh --------------------------------------------------------------------- Greenspun's Tenth Rule of Programming: any sufficiently complicated C or Fortran program contains an ad hoc informally-specified bug-ridden slow implementation of half of Common Lisp. ---------------------------------------------------------------------

1 0