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

[mcclim-devel] Edit form in the clim listener
by Philippe Brochard 04 Sep '06

04 Sep '06

Hi all, In cl-wav-synth, I use the code below to edit a form previously evaluated in the listener. It works very well for me but is this an acceptable way to do it and is there something planed to add the editing capability in the listener ? (I've looked in the source and found something about history but I doesn't found how to use it). Best regards, Philippe ---------------------------------------------------------------------- (define-command (com-eval :menu t :command-table lisp-commands) ((form 'clim:form :prompt "Form")) (let ((values (multiple-value-list (handler-case (eval form) (error (condition) (format nil "~A" condition)))))) (fresh-line) (shuffle-specials form values) (display-evalues values) (fresh-line))) (define-command (com-edit-form :name t :menu t :command-table lisp-commands) ((form 'form :prompt "Form")) (multiple-value-bind (x1 y1) (stream-cursor-position *standard-input*) (let ((new-form (accept 'clim:form :stream (frame-standard-input *application-frame*) :prompt "New form" :default form :insert-default t))) (multiple-value-bind (x2 y2) (stream-cursor-position *standard-input*) (declare (ignore x2)) (let* ((interactor (find-pane-named *application-frame* 'cl-wav-synth-clim::interactor)) (output-history (stream-output-history interactor)) (width (bounding-rectangle-width interactor))) (decf y1 (stream-line-height interactor)) (map-over-output-records-overlapping-region #'(lambda (rec) (delete-output-record rec output-history)) output-history (make-rectangle* 0 y1 width y2)) (draw-rectangle* interactor 0 y1 width y2 :ink (pane-background interactor)) (setf (stream-cursor-position *standard-input*) (values x1 y1)) (print-listener-prompt interactor *application-frame*) (present new-form 'form) (fresh-line) (force-output) (execute-frame-command *application-frame* `(com-eval ,new-form))))))) (define-presentation-to-command-translator edit-form (clim:command com-edit-form lisp-commands :gesture :describe :echo t :documentation ((object stream) (format stream "Edit ~A" (second object))) :pointer-documentation ((object stream) (format stream "Edit ~A" (second object))) :tester ((object) (eql (car object) 'com-eval))) (object) (list (second object))) (define-presentation-to-command-translator edit-form-form (clim:form com-edit-form lisp-commands :gesture :describe :echo t :documentation ((object stream) (format stream "Edit ~A" object)) :pointer-documentation ((object stream) (format stream "Edit ~A" object))) (object) (list object)) (define-presentation-to-command-translator eval-form (clim:form com-eval lisp-commands :gesture :select :echo t :documentation ((object stream) (format stream "Eval ~A" object)) :pointer-documentation ((object stream) (format stream "Eval ~A" object))) (object) (list object)) ---------------------------------------------------------------------- -- Philippe Brochard <hocwp(a)free.fr> http://hocwp.free.fr -=-= http://www.gnu.org/home.fr.html =-=-

1 0

[mcclim-devel] [ANN] cl-wav-synth - express noises as you think V2006-08-26
by Philippe Brochard 04 Sep '06

04 Sep '06

Hi everybody, I'm glad to announce the last public release of cl-wav-synth. cl-wav-synth is a wav sample editor. It comes in two parts, the main library for manipulating wav files and a (Mc)CLIM interface with a full lisp listener, a sample pane editor, a spectrum pane editor and a song pane editor. The wav sample editor is driven from the lisp REPL: you can watch immediately the result of each applied functions. cl-wav-synth comes with some effects as echo, delay, pitch... The spectrum editor is here just for educational purpose. It show the effect of adding sinus together. But it can load spectrum from the sharc project and can be used to produce instruments sounds (the sample amplitude need to be modified to have a real sound). The song editor is a way to express a song. A song is just a list of events to write on a wav file. cl-wav-synth traverses the song list and evaluates the form of each song-sample, if the result is a wav sample, it is merged in the song wav file. Since the last release, there have been many enhancements For samples: - Sample flags (or multiselections) - Sample tones - To produce all the musical range (do, ré, mi... or a, b, c...) from a single sample. - Envelope manipulation (drawing mode) - Players choices (tested under Unix/MacOS/Windows) For songs: - Mouse rectangular selection (move/delete/copy selection) - Undo/Redo system - Grid and snap And some bug fixes (in particular a double redisplay which divided the performances by two (sorry for the bad pub)). You can find more here: http://common-lisp.net/project/cl-wav-synth/ Have fun, and thanks all for your great work with McCLIM ! I'm really amazed how easy it is to make graphical things with clim (once your accustomed to it). Regards, Philippe -- Philippe Brochard <hocwp(a)free.fr> http://hocwp.free.fr -=-= http://www.gnu.org/home.fr.html =-=-

1 1

[mcclim-devel] international text help
by Hazen Babcock 24 Aug '06

24 Aug '06

Hello, I'd like to display some chinese characters in my mcclim application, but I'm not sure how to go about this. I've loaded :mcclim-freetype and tried to follow: http://common-lisp.net/pipermail/mcclim-devel/ 2005-August/004136.html since I have a truetype font that includes chinese characters. (defmethod display-some-pane ((frame translator-frame) stream) (declare (ignore stream)) (let ((pane (get-frame-pane *application-frame* 'some-pane))) (window-clear pane) (with-text-style (pane (make-device-font-text-style (port *application-frame*) "/usr/share/fonts/truetype/ttf-bitstream-vera/VeraBd.ttf")) (draw-text* pane "foo" 10 10)))) gives: The value "/usr/share/fonts/truetype/ttf-bitstream-vera/VeraBd.ttf" is not of type MCCLIM-FREETYPE::FREETYPE-DEVICE-FONT-NAME. [Condition of type TYPE-ERROR] If I use a function that I don't think I'm supposed to use directly: (defmethod display-some-pane ((frame translator-frame) stream) (declare (ignore stream)) (let ((pane (get-frame-pane *application-frame* 'some-pane))) (window-clear pane) (with-text-style (pane (make-device-font-text-style (port *application-frame*) (mcclim-freetype::make-freetype-device-font-name :font-file "/usr/share/fonts/truetype/ttf-bitstream-vera/ VeraBd.ttf" :size 12))) (draw-text* pane "foo" 10 10)))) then it works, but I imagine that this is not the right/supported way. thanks, -Hazen

1 0

[mcclim-devel] documentation fix
by Willem Broekema 24 Jul '06

24 Jul '06

Hi all, In file INSTALL there's 'asdf:load instead of 'asdf:load-op, and a missing closing bracket. This patch fixes that. - Willem

2 1

[mcclim-devel] CLIM-STREAM-PANE bugs mentioned in CLIM guided tour
by Paolo Amoroso 14 Jul '06

14 Jul '06

The version of the paper "A Guided Tour of CLIM" in McCLIM's source tree, which I believe is updated to early 2006, states in section "A simple drawing application": This is the first example that does not use clim-stream-pane (or one of its subclasses) as a pane class[*] [...] [*] When using McCLIM, we have to do this as there are bugs in the behavior of clim-stream-pane that have not been fixed yet. What are these bugs? Are they still outstanding? Paolo -- Lisp Propulsion Laboratory log - http://www.paoloamoroso.it/log

1 0

[mcclim-devel] Patch for menu-choose.lisp
by Troels Henriksen 09 Jul '06

09 Jul '06

The current implementation of `menu-choose' lacks a fair bunch of spec-defined functionality (labels, some menu item types, scrollbars), and it often creates menus that are larger than the screen, or partially off-screen. This patch rectifies these problems - I have been running with it for 6+ months and it has worked perfectly, even though some of the code is not the prettiest in the world (my CLIM-fu has been weak). There should be no functionality regressions compared to the current version. I know that McCLIM is currently in a freeze period, but this patch has been lying on my harddrive for too long - others may find it useful, and I would like it to be cleaned up (if necessary) so it could be included in some future release. :-) -- \ Troels "Athas" /\ Henriksen

8 12

[mcclim-devel] follow-up about format-graph-from-roots question
by rpgoldman＠real-time.com 26 Jun '06

26 Jun '06

Seems like this may be more a problem with scrolling panes than with format-graph-from-roots. Previously, I incorrectly reported that I was having trouble with the built-in graph types, but not with my own. That was wrong --- it seemed to be true only because my graphs were smaller. So it now seems that the problem arises with any graph that is installed inside an application pane with :scroll-bars :both. Has anyone else seen problems with scrolling application panes, either especially with graphs in them or just in general? I am starting to suspect that my change-space-requirements fu is weak.... thanks, R

1 0

[mcclim-devel] for bears of very little brain (pathname accepter w/ completion)
by rpgoldman＠real-time.com 26 Jun '06

26 Jun '06

Is there anywhere a completing read for pathnames, possibly with type defaults? I know that mgr has a nice file-selector-gadget, but I'm a little reluctant to use it, since it's still not fused with McCLIM proper (unless that's changed?). I think also that there's something inside CLIMACS, but it hasn't been freed up for more generic McCLIM use (or has it?). Thanks, R

1 0

[mcclim-devel] questions about space requirements and graph layout
by rpgoldman＠real-time.com 26 Jun '06

26 Jun '06

I was careless and did not check up on my application that used graph layout while a couple of rounds of changes were made. Now I find that my application is all stuffed up, and I was hoping that someone could make some suggestions. In particular: 1. My old code would draw graphs, and at the end of each graph-drawing function would invoke: (change-space-requirements stream :min-width (bounding-rectangle-width rect) :min-height (bounding-rectangle-height rect)) In the past this seemed to Do The Right Thing: the application pane (at the top, over an interactor pane) would get larger, and scroll bars would appear as needed. Now, however, something that seems very wrong to me happens, viz: a. I stretch the frame larger than its original size. b. I invoke a graph drawer. c. The frame resizes itself to its original size. My conjecture is that the effect of changing space requirements may have changed. Weirdly, the space requirement is now: [1i] GRAPH-MDP(74): :i 22 A NEW CLIMI::STANDARD-SPACE-REQUIREMENT @ #x881c250a = #<CLIMI::STANDARD-SPACE-REQUIREMENT width: 0.0d0 [0.0d0,100000000] height: 0.0d0 [0.0d0,100000000]> 0 Class --------> #<STANDARD-CLASS CLIMI::STANDARD-SPACE-REQUIREMENT> 1 WIDTH --------> double-float = 0.0d0 [#x00000000 00000000] 2 MAX-WIDTH ----> fixnum 100000000 [#x17d78400] 3 MIN-WIDTH ----> double-float = 0.0d0 [#x00000000 00000000] 4 HEIGHT -------> double-float = 0.0d0 [#x00000000 00000000] 5 MAX-HEIGHT ---> fixnum 100000000 [#x17d78400] 6 MIN-HEIGHT ---> double-float = 0.0d0 [#x00000000 00000000] although the current-width is 6952.0 and the current-height is 4261.5. I was considering that perhaps I should have been changing the width and height slots of the space-requirement instead of min- values, but (a) this used to work and (b) it seems like none of my changed space requirements are "taking." Here's what happens when I trace change-space-requirements: 0[9]: (CLIM:CHANGE-SPACE-REQUIREMENTS #<CLIM:APPLICATION-PANE SIFT.MDP:MDP @ #x72d0bc22> :WIDTH 6952.0 :HEIGHT 4261.5 :MIN-WIDTH 6952.0 :MIN-HEIGHT 4261.5) 0* (CALL-METHOD #<STANDARD-METHOD CLIM:CHANGE-SPACE-REQUIREMENTS :AROUND (CLIM:CLIM-STREAM-PANE)> ((MULTIPLE-VALUE-PROG1 (PROGN #<STANDARD-METHOD CLIM:CHANGE-SPACE-REQUIREMENTS :BEFORE (CLIM-INTERNALS::SPACE-REQUIREMENT-OPTIONS-MIXIN)> #<STANDARD-METHOD CLIM:CHANGE-SPACE-REQUIREMENTS :BEFORE (CLIM-INTERNALS::LAYOUT-PROTOCOL-MIXIN)> #<STANDARD-METHOD CLIM:CHANGE-SPACE-REQUIREMENTS (CLIM-INTERNALS::LAYOUT-PROTOCOL-MIXIN)>) #<STANDARD-METHOD CLIM:CHANGE-SPACE-REQUIREMENTS :AFTER (CLIM-INTERNALS::LAYOUT-PROTOCOL-MIXIN)>))) 1[9]: (CLIM:CHANGE-SPACE-REQUIREMENTS #<CLIM-EXTENSIONS:VIEWPORT-PANE "(Unnamed Pane)" @ #x72d0c35a> :RESIZE-FRAME NIL) 1* (MULTIPLE-VALUE-PROG1 (PROGN #<STANDARD-METHOD CLIM:CHANGE-SPACE-REQUIREMENTS :BEFORE (CLIM-INTERNALS::SPACE-REQUIREMENT-OPTIONS-MIXIN)> #<STANDARD-METHOD CLIM:CHANGE-SPACE-REQUIREMENTS :BEFORE (CLIM-INTERNALS::LAYOUT-PROTOCOL-MIXIN)> #<STANDARD-METHOD CLIM:CHANGE-SPACE-REQUIREMENTS (CLIM-EXTENSIONS:VIEWPORT-PANE)>) #<STANDARD-METHOD CLIM:CHANGE-SPACE-REQUIREMENTS :AFTER (CLIM-INTERNALS::LAYOUT-PROTOCOL-MIXIN)>) 1[9]: returned NIL 0[9]: returned NIL Possibly the information about the space requirements is not properly percolating up from the application-pane to its enclosing viewport-pane? [1i] GRAPH-MDP(85): :i A TENURED CLIM-EXTENSIONS:VIEWPORT-PANE @ #x72d0c35a = #<CLIM-EXTENSIONS:VIEWPORT-PANE "(Unnamed Pane)" @ #x72d0c35a> 0 Class --------> #<STANDARD-CLASS CLIM-EXTENSIONS:VIEWPORT-PANE> 1 REGION -------> #<STANDARD-BOUNDING-RECTANGLE X 0:646.0d0 Y 0:590 @ #x735b3e8a> 2 NATIVE-TRANSFORMATION -> #<CLIMI::STANDARD-IDENTITY-TRANSFORMATION 1 0 0 1 0 0> 3 NATIVE-REGION -> #<STANDARD-RECTANGLE X 0:646.0d0 Y 0:590 @ #x735b3e9a> 4 DEVICE-TRANSFORMATION -> The symbol NIL 5 DEVICE-REGION -> The symbol NIL 6 POINTER-CURSOR -> The symbol :DEFAULT 7 ENABLED-P ----> The symbol T 8 CURRENT-WIDTH -> The symbol NIL 9 CURRENT-HEIGHT -> The symbol NIL 10 TRANSFORMATION -> #<CLIMI::STANDARD-TRANSLATION 1 0 0 1 4 4> 11 QUEUE --------> #<CLIMI::PORT-EVENT-QUEUE @ #x72d06c52> 12 NAME ---------> A simple-string (14) "(Unnamed Pane)" 13 MANAGER ------> #<CLIM-CLX::CLX-FRAME-MANAGER @ #x72c0b642> 14 FRAME --------> #<TAEMS-MDP-APP @ #x72ceb5b2> 15 ENABLEDP -----> The symbol NIL 16 SPACE-REQUIREMENT -> The symbol NIL 17 NEW-WIDTH ----> The symbol NIL 18 NEW-HEIGHT ---> The symbol NIL 19 REDISPLAY-NEEDED -> The symbol NIL 20 PORT ---------> #<CLIM-CLX::CLX-PORT :HOST "" :DISPLAY-ID 0 @ #x72c02ada> 21 MIRROR-TRANSFORMATION -> #<CLIMI::STANDARD-TRANSLATION 1 0 0 1 4 4> 22 MIRROR-REGION -> #<STANDARD-RECTANGLE X 0:646 Y 0:590 @ #x735b3eca> 23 PARENT -------> #<SCROLLER-PANE "(Unnamed Pane)" @ #x72d0c7aa> 24 USER-WIDTH ---> The symbol NIL 25 USER-MIN-WIDTH -> The symbol NIL 26 USER-MAX-WIDTH -> The symbol NIL 27 USER-HEIGHT --> The symbol NIL 28 USER-MIN-HEIGHT -> The symbol NIL 29 USER-MAX-HEIGHT -> The symbol NIL 30 X-SPACING ----> fixnum 0 [#x00000000] 31 Y-SPACING ----> fixnum 0 [#x00000000] 32 FOREGROUND ---> #<CLIMI::NAMED-COLOR "black"> 33 BACKGROUND ---> #<CLIMI::NAMED-COLOR "gray84"> 34 TEXT-STYLE ---> #<STANDARD-TEXT-STYLE :FIX :ROMAN :NORMAL> 35 ALIGN-X ------> The symbol :LEFT 36 ALIGN-Y ------> The symbol :TOP 37 CHILD --------> #<APPLICATION-PANE MDP @ #x72d0bc22> [1i] GRAPH-MDP(86): :i 37 A TENURED APPLICATION-PANE @ #x72d0bc22 = #<APPLICATION-PANE MDP @ #x72d0bc22> 0 Class --------> #<STANDARD-CLASS APPLICATION-PANE> 1 MARKINGS -----> The symbol NIL 2 POINT-1-X ----> The symbol NIL 3 POINT-1-Y ----> The symbol NIL 4 POINT-2-X ----> The symbol NIL 5 POINT-2-Y ----> The symbol NIL 6 DRAGGING-P ---> The symbol NIL 7 REGION -------> #<STANDARD-BOUNDING-RECTANGLE X 0:6952.0 Y 0:4261.5 @ #x87f3415a> 8 NATIVE-TRANSFORMATION -> #<CLIMI::STANDARD-IDENTITY-TRANSFORMATION 1 0 0 1 0 0> 9 NATIVE-REGION -> #<STANDARD-RECTANGLE X 0:646.0d0 Y 0:590 @ #x87f34172> 10 DEVICE-TRANSFORMATION -> The symbol NIL 11 DEVICE-REGION -> #<STANDARD-RECTANGLE X 0:646.0d0 Y 0:590 @ #x87f34172> 12 POINTER-CURSOR -> The symbol :DEFAULT 13 ENABLED-P ----> The symbol T 14 CURRENT-WIDTH -> single-float = 6952.0 [#x45d94000] 15 CURRENT-HEIGHT -> single-float = 4261.5 [#x45852c00] 16 TRANSFORMATION -> #<CLIMI::STANDARD-IDENTITY-TRANSFORMATION 1 0 0 1 0 0> 17 QUEUE --------> #<CLIMI::PORT-EVENT-QUEUE @ #x72d06c52> 18 NAME ---------> The symbol MDP 19 MANAGER ------> #<CLIM-CLX::CLX-FRAME-MANAGER @ #x72c0b642> 20 FRAME --------> #<TAEMS-MDP-APP @ #x72ceb5b2> 21 ENABLEDP -----> The symbol NIL 22 SPACE-REQUIREMENT -> #<CLIMI::STANDARD-SPACE-REQUIREMENT width: 0.0d0 [0.0d0,100000000] height: 0.0d0 [0.0d0,100000000]> 23 NEW-WIDTH ----> The symbol NIL 24 NEW-HEIGHT ---> The symbol NIL 25 PORT ---------> #<CLIM-CLX::CLX-PORT :HOST "" :DISPLAY-ID 0 @ #x72c02ada> 26 MIRROR-TRANSFORMATION -> #<CLIMI::STANDARD-IDENTITY-TRANSFORMATION 1 0 0 1 0 0> 27 MIRROR-REGION -> #<STANDARD-RECTANGLE X 0:3799 Y 0:2425 @ #x87f341c2> 28 PARENT -------> #<CLIM-EXTENSIONS:VIEWPORT-PANE "(Unnamed Pane)" @ #x72d0c35a> 29 X-SPACING ----> fixnum 0 [#x00000000] 30 Y-SPACING ----> fixnum 0 [#x00000000] 31 ALIGN-X ------> The symbol :LEFT 32 ALIGN-Y ------> The symbol :TOP 33 CHILDREN -----> The symbol NIL 34 RECORDING-P --> The symbol T 35 DRAWING-P ----> The symbol T 36 OUTPUT-HISTORY -> #<STANDARD-TREE-OUTPUT-HISTORY X 0.0d0:6952.0 Y 0.0d0:4261.5 @ #x72d0c36a> 37 CURRENT-OUTPUT-RECORD -> #<STANDARD-TREE-OUTPUT-HISTORY X 0.0d0:6952.0 Y 0.0d0:4261.5 @ #x72d0c36a> 38 CURRENT-TEXT-OUTPUT-RECORD -> The symbol NIL 39 LOCAL-RECORD-P -> The symbol T ... 123 (MISC C APPLICATION-PANE) -> #<Function STM-FUNDAMENTAL-MISC> 2. I have three flavors of layouts, two use the built in graph types, and one uses my own, experimental tree-with-cross-edges graph subtype. Previously they all three worked (for some definition of "worked," that does not extend to "lays out graphs in an aesthetically-pleasing way :->). Now only my own tree-with-cross-edges works; the other two seem to display nothing, although I can see a traced call to format-graph-from-roots, I find reasonable bounds (which *should* trigger the addition of scroll bars, AFAICT), and if I take a long and laborious trip down into the guts of the pane's output record, I find a CLIMI::DAG-GRAPH-OUTPUT-RECORD inside a STANDARD-SEQUENCE-OUTPUT-RECORD inside a STANDARD-UPDATING-OUTPUT-RECORD. As I said, this used to work, but alas, that was even before the addition of spatial-trees, so I'm not sure where this went south. Any suggestions about how I might figure out why this is not showing up? Actually, it might be as simple as the graph being so large that none of it actually appears in the part of the pane that is actually displayed... So perhaps the answer to this question reduces to answering question 1...

1 0

[mcclim-devel] interactive-stream-p
by Christophe Rhodes 23 Jun '06

23 Jun '06

Hi, The Gray stream function interactive-stream-p is "specified" in CLIM. Would it be reasonable to make it return T for most of the extended streams that CLIM provides and NIL for postscript streams (and potentially other batched output streams such as pdf, when a backend for that shows up)? At present I believe it returns NIL for everything. The use case I have is being able to use the same drawing routine for screen and print, customizing behaviour based on the value of (interactive-stream-p stream). Cheers, Christophe

2 1