mcclim-devel

mcclim-devel@common-lisp.net

820 discussions

Re: SV: SV: [mcclim-devel] Problems getting "format-graph-from-roots"towork...
by Paolo Amoroso 07 Feb '06

07 Feb '06

"Peter Braroe" <peter.braroe(a)newsmachine.com> writes: > Tried it but didnt seem to work... :-( I will mail you a screenshot direct [...] > "Peter Braroe" <peter.braroe(a)newsmachine.com> writes: > >> Now all I need to do is to figure out how to get it to draw in color... > does >> anyone know if that is supported with :ink or some other method? > > Try wrapping the drawing operations into a WITH-DRAWING-OPTIONS form. I have received your screen shot. If you want colored arcs, you may use the :ARC-DRAWING-OPTIONS of FORMAT-GRAPH-FROM-ROOTS. If you are instead interested in colored nodes, try something like this for :OBJECT-PRINTER (untested): #'(lambda (x s) (with-drawing-options (*test-frame* :ink +red+) (princ (car x) s))) Paolo -- Lisp Propulsion Laboratory log - http://www.paoloamoroso.it/log

1 0

Re: SV: [mcclim-devel] Problems getting "format-graph-from-roots" towork...
by Paolo Amoroso 07 Feb '06

07 Feb '06

"Peter Braroe" <peter.braroe(a)newsmachine.com> writes: > Now all I need to do is to figure out how to get it to draw in color... does > anyone know if that is supported with :ink or some other method? Try wrapping the drawing operations into a WITH-DRAWING-OPTIONS form. Paolo -- Lisp Propulsion Laboratory log - http://www.paoloamoroso.it/log

2 1

[mcclim-devel] postscript streams
by Christophe Rhodes 06 Feb '06

06 Feb '06

Hi, I'm in the process of attempting to merge our local divergences into mcclim's CVS, and I have a question about one of them (see below): is it reasonable to add updating-output-stream-mixin to the postscript-stream class? Though memory grows dim, I think we use this to allow the same drawing routines (which use updating-output) to draw both to screen and to postscript; we don't actually call incremental-redisplay on a postscript stream. Thanks, Christophe Index: Backends/PostScript/class.lisp =================================================================== RCS file: /project/mcclim/cvsroot/mcclim/Backends/PostScript/class.lisp,v retrieving revision 1.7 diff -u -r1.7 class.lisp --- Backends/PostScript/class.lisp 31 Oct 2005 10:21:14 -0000 1.7 +++ Backends/PostScript/class.lisp 6 Feb 2006 12:30:36 -0000 @@ -61,6 +61,7 @@ permanent-medium-sheet-output-mixin sheet-mute-repainting-mixin mirrored-sheet-mixin ; ? + climi::updating-output-stream-mixin ; ?? standard-extended-output-stream standard-output-recording-stream) ((file-stream :initarg :file-stream :reader postscript-stream-file-stream)

2 2

[mcclim-devel] CLX translate function
by Christophe Rhodes 06 Feb '06

06 Feb '06

Hi, Another divergence minimization patch for review, this time slightly more involved. It is to do with the translation function for the CLX backend, and while it doesn't intend to introduce any functionality (or lack of it) that there was before, I'd feel happier to know that someone other than me understood my comment. Cheers, Christophe

1 0

[mcclim-devel] Proper naming of threads under SBCL (patch)
by Troels Henriksen 04 Feb '06

04 Feb '06

Attached is a patch which will pass the names of threads created with `make-process' properly on to `sb-thread:make-thread' under SBCL. Without this patch, the specified names of threads will not show up when doing a thread listing with `sb-thread:list-all-threads'. It's an extremely simple patch and it hasn't caused any problems for me. -- \ Troels "Athas" Henriksen /\ sigkill.dk/blog (Danish)

1 0

[mcclim-devel] The function (SETF RECTANGLE-EDGES*) is undefined.
by Irene DURAND 03 Feb '06

03 Feb '06

Hello, With an updated version of mcclim and SBCL 0.9.5, my software Autowrite does not run anymore (see stackframe below). The same software compiles and runs fine with CMUCL and a previous clim core. -- Irène http://dept-info.labri.u-bordeaux.fr/~idurand The function (SETF RECTANGLE-EDGES*) is undefined. [Condition of type UNDEFINED-FUNCTION] Restarts: 0: [ABORT] Return to application command loop 1: [ABORT-REQUEST] Abort handling SLIME request. 2: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" {A462359}>) Backtrace: 0: ("bogus stack frame") 1: ((LAMBDA (SB-PCL::.PV-CELL. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0. SB-PCL::.ARG1.)) #<unavailable argument> #<unavailable argument> 0 #<GOATEE::SCREEN-LINE X 81:81 Y 0:0 "" {A9CDB11}>) 2: ((SB-PCL::FAST-METHOD INITIALIZE-INSTANCE :AFTER (GOATEE::SCREEN-LINE)) (#(NIL 0 10 4 11) . #()) #<unavailable argument> #<GOATEE::SCREEN-LINE X 81:81 Y 0:0 "" {A9CDB11}> (:X-POSITION 81 :Y-POSITION 0 :PARENT #<GOATEE:SIMPLE-SCREEN-AREA X 81:81 Y 0:0 {A797881}> :BUFFER-LINE #<GOATEE::EXTENT-BUFFER-LINE ""> :LAST-TICK 2 ...)) 3: ((LAMBDA (SB-PCL::|.P0.| SB-PCL::|.P1.| SB-PCL::|.P2.| SB-PCL::|.P3.| SB-PCL::|.P4.| SB-PCL::|.P5.| SB-PCL::|.P6.| SB-PCL::|.P7.|)) #<unavailable argument> #<unavailable argument> #<unavailable argument> #<unavailable argument> #<unavailable argument> #<unavailable argument> #<unavailable argument> #<unavailable argument>) 4: ((SB-PCL::FAST-METHOD GOATEE::INITIALIZE-AREA-FROM-BUFFER (GOATEE:SIMPLE-SCREEN-AREA T)) (#(NIL 16) . #()) #<unavailable argument> #<GOATEE:SIMPLE-SCREEN-AREA X 81:81 Y 0:0 {A797881}> #<GOATEE::EDITABLE-BUFFER {A53CC29}>) 5: ((SB-PCL::FAST-METHOD INITIALIZE-INSTANCE :AFTER (GOATEE:SIMPLE-SCREEN-AREA)) (#(NIL 17 15 22 21 19 16) . #()) #<unavailable argument> #<GOATEE:SIMPLE-SCREEN-AREA X 81:81 Y 0:0 {A797881}> (:AREA-STREAM #<INTERACTOR-PANE INTERACTOR-PANE {ACCB111}> :BUFFER #<GOATEE::EDITABLE-BUFFER {A53CC29}> :X-POSITION 81 :Y-POSITION 0 :CURSOR-VISIBILITY T ...)) 6: ((LAMBDA (SB-PCL::.PV-CELL. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0. SB-PCL::.DFUN-REST-ARG.)) #<unavailable argument> #<unavailable argument> #<GOATEE:SIMPLE-SCREEN-AREA X 81:81 Y 0:0 {A797881}> (:AREA-STREAM #<INTERACTOR-PANE INTERACTOR-PANE {ACCB111}> :BUFFER #<GOATEE::EDITABLE-BUFFER {A53CC29}> :X-POSITION 81 :Y-POSITION 0 :CURSOR-VISIBILITY T ...)) 7: ((SB-PCL::FAST-METHOD MAKE-INSTANCE (CLASS)) #<unavailable argument> #<unavailable argument> #<STANDARD-CLASS GOATEE:SIMPLE-SCREEN-AREA> (:AREA-STREAM #<INTERACTOR-PANE INTERACTOR-PANE {ACCB111}> :BUFFER #<GOATEE::EDITABLE-BUFFER {A53CC29}> :X-POSITION 81 :Y-POSITION 0 :CURSOR-VISIBILITY T ...)) 8: ((SB-PCL::FAST-METHOD INITIALIZE-INSTANCE :AFTER (GOATEE:GOATEE-INPUT-EDITING-MIXIN)) #<unavailable argument> #<unavailable argument> #<STANDARD-INPUT-EDITING-STREAM {986DAE1}> (:STREAM #<INTERACTOR-PANE INTERACTOR-PANE {ACCB111}> :INITIAL-CONTENTS "")) 9: ((LAMBDA (SB-PCL::.PV-CELL. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0. SB-PCL::.DFUN-REST-ARG.)) #<unavailable argument> #<unavailable argument> #<STANDARD-INPUT-EDITING-STREAM {986DAE1}> (:STREAM #<INTERACTOR-PANE INTERACTOR-PANE {ACCB111}> :INITIAL-CONTENTS "")) 10: ((SB-PCL::FAST-METHOD MAKE-INSTANCE (CLASS)) #<unavailable argument> #<unavailable argument> #<STANDARD-CLASS STANDARD-INPUT-EDITING-STREAM> (:STREAM #<INTERACTOR-PANE INTERACTOR-PANE {ACCB111}> :INITIAL-CONTENTS "")) 11: ((SB-PCL::FAST-METHOD CLIM-INTERNALS::INVOKE-WITH-INPUT-EDITING (EXTENDED-INPUT-STREAM T T T T)) #<unavailable argument> #<unavailable argument> #<INTERACTOR-PANE INTERACTOR-PANE {ACCB111}> #<CLOSURE (LAMBDA (STREAM)) {97BBD85}> #<CLOSURE (LAMBDA (STREAM CLIM-INTERNALS::CONT)) {97BBDD5}> "" STANDARD-INPUT-EDITING-STREAM) 12: ((SB-PCL::FAST-METHOD CLIM-INTERNALS::INVOKE-WITH-INPUT-EDITING :AROUND (EXTENDED-OUTPUT-STREAM T T T T)) #<unavailable argument> #S(SB-PCL::FAST-METHOD-CALL :FUNCTION #<FUNCTION (SB-PCL::FAST-METHOD CLIM-INTERNALS::INVOKE-WITH-INPUT-EDITING #)> :PV-CELL NIL :NEXT-METHOD-CALL #S(SB-PCL::FAST-METHOD-CALL :FUNCTION #<FUNCTION #> :PV-CELL NIL :NEXT-METHOD-CALL NIL :ARG-INFO (5)) :ARG-INFO (5)) #<INTERACTOR-PANE INTERACTOR-PANE {ACCB111}> #<CLOSURE (LAMBDA (STREAM)) {97BBD85}> #<CLOSURE (LAMBDA (STREAM CLIM-INTERNALS::CONT)) {97BBDD5}> "" STANDARD-INPUT-EDITING-STREAM) 13: (ACCEPT (COMMAND :COMMAND-TABLE #<STANDARD-COMMAND-TABLE AUTOWRITE {A023991}>) :STREAM #<INTERACTOR-PANE INTERACTOR-PANE {ACCB111}> :PROMPT NIL :DEFAULT (CLIM-INTERNALS::COM-NULL-COMMAND) :DEFAULT-TYPE CLIM-INTERNALS::NULL-COMMAND) 14: (READ-COMMAND #<STANDARD-COMMAND-TABLE AUTOWRITE {A023991}> :STREAM #<INTERACTOR-PANE INTERACTOR-PANE {ACCB111}> :COMMAND-PARSER NIL :COMMAND-UNPARSER NIL :PARTIAL-COMMAND-PARSER NIL :USE-KEYSTROKES NIL) 15: (READ-COMMAND-USING-KEYSTROKES #<STANDARD-COMMAND-TABLE AUTOWRITE {A023991}> NIL :STREAM #<INTERACTOR-PANE INTERACTOR-PANE {ACCB111}> :COMMAND-PARSER NIL :COMMAND-UNPARSER NIL :PARTIAL-COMMAND-PARSER NIL) 16: (READ-COMMAND #<STANDARD-COMMAND-TABLE AUTOWRITE {A023991}> :STREAM #<INTERACTOR-PANE INTERACTOR-PANE {ACCB111}> :COMMAND-PARSER NIL :COMMAND-UNPARSER NIL :PARTIAL-COMMAND-PARSER NIL :USE-KEYSTROKES T) 17: ((SB-PCL::FAST-METHOD READ-FRAME-COMMAND :AROUND (APPLICATION-FRAME)) #<unavailable argument> #S(SB-PCL::FAST-METHOD-CALL :FUNCTION #<FUNCTION (SB-PCL::FAST-METHOD READ-FRAME-COMMAND #)> :PV-CELL NIL :NEXT-METHOD-CALL NIL :ARG-INFO (1 . T)) #<AUTOWRITE {961A071}> (:STREAM #<INTERACTOR-PANE INTERACTOR-PANE {ACCB111}>)) 18: ((SB-PCL::FAST-METHOD DEFAULT-FRAME-TOP-LEVEL (APPLICATION-FRAME)) #<unavailable argument> #<unavailable argument> #<AUTOWRITE {961A071}> NIL) 19: ((SB-PCL::FAST-METHOD DEFAULT-FRAME-TOP-LEVEL (APPLICATION-FRAME)) #<unavailable argument> #<unavailable argument> #<AUTOWRITE {961A071}> NIL) 20: ((LAMBDA (SB-PCL::.PV-CELL. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0. SB-PCL::.DFUN-REST-ARG.)) #<unavailable argument> #<unavailable argument> #<AUTOWRITE {961A071}> NIL) 21: ((SB-PCL::FAST-METHOD RUN-FRAME-TOP-LEVEL (APPLICATION-FRAME)) #<unavailable argument> #<unavailable argument> #<AUTOWRITE {961A071}> #<unavailable argument>) 22: ((SB-PCL::FAST-METHOD RUN-FRAME-TOP-LEVEL :AROUND (APPLICATION-FRAME)) #<unavailable argument> #S(SB-PCL::FAST-METHOD-CALL :FUNCTION #<FUNCTION (SB-PCL::FAST-METHOD RUN-FRAME-TOP-LEVEL #)> :PV-CELL NIL :NEXT-METHOD-CALL NIL :ARG-INFO (1 . T)) #<AUTOWRITE {961A071}> NIL) 23: (INTERFACE) 24: (SB-INT:EVAL-IN-LEXENV (START) #<NULL-LEXENV>) 25: (SWANK::EVAL-REGION "(start) " T) 26: ((LAMBDA NIL)) 27: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-SYNTAX-HOOKS (T)) #<unused argument> #<unused argument> #<CLOSURE (LAMBDA NIL) {A6EF1FD}>) 28: (SWANK::CALL-WITH-BUFFER-SYNTAX #<CLOSURE (LAMBDA NIL) {A6EF1FD}>) 29: (SB-INT:EVAL-IN-LEXENV (SWANK:LISTENER-EVAL "(start) ") #<NULL-LEXENV>) 30: ((LAMBDA NIL)) 31: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK (T T)) #<unused argument> #<unused argument> #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA NIL) {A6EEB9D}>) 32: ((LAMBDA NIL)) 33: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK (T T)) #<unused argument> #<unused argument> #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<FUNCTION (LAMBDA NIL) {9E5E8DD}>) 34: (SWANK::CALL-WITH-REDIRECTED-IO #<SWANK::CONNECTION {A310E51}> #<CLOSURE (LAMBDA NIL) {A6EEA5D}>) 35: (SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {A310E51}> #<FUNCTION (LAMBDA NIL) {9E5E8DD}>) 36: (SWANK::HANDLE-REQUEST #<SWANK::CONNECTION {A310E51}>) 37: ((LAMBDA NIL)) 38: ((LAMBDA NIL)) 39: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK (T T)) #<unused argument> #<unused argument> #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA NIL) {A46B07D}>) 40: (SWANK::CALL-WITH-REDIRECTED-IO #<SWANK::CONNECTION {A310E51}> #<CLOSURE (LAMBDA NIL) {A46B08D}>) 41: (SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {A310E51}> #<CLOSURE (LAMBDA NIL) {A46B07D}>) 42: (SWANK::CALL-WITH-BINDINGS NIL #<CLOSURE (LAMBDA NIL) {A46B05D}>) 43: ((LAMBDA NIL)) 44: ("foreign function: call_into_lisp") 45: ("foreign function: funcall0") 46: ("foreign function: new_thread_trampoline") 47: ("foreign function: #x53EB80")

2 1

[mcclim-devel] Newbie problems with "accepting-values" / no method for CLIM:STREAM-CURSOR-POSITION
by Peter Braroe 03 Feb '06

03 Feb '06

Hello all! I am trying to get into mcCLIM to write a frontend to a text (news) analysis tool... I use CMUCL and have followed the INSTALL.CMU file and most of the demos work fine. But as I get down to it and start writing code to use "accepting-values" for instance I get the message below. I also get it when running the demos so i assume that something is wrong with the environment... but what? It's probably something simple but I have tried to figgure it out for a lot of hours and some ideas would be greatly appreciated! Thanks, /Peter PS I tried wihout SLIME but that didn't work either. See second trace below. CL-USER> (clim-demo::accepting-interval) No matching method for the generic function #<STANDARD-GENERIC-FUNCTION CLIM:STREAM-CURSOR-POSITION (2) {58BBC3B9}>, when called with arguments (#<Two-Way Stream, Input = #<SWANK-BACKEND::SLIME-INPUT-STREAM {58B7D7B5}>, Output = #<Stream for descriptor 7>>). [Condition of type PCL::NO-APPLICABLE-METHOD-ERROR] Restarts: 0: [CONTINUE] Retry call to :FUNCTION. 1: [ABORT] Abort handling SLIME request. 2: [ABORT] Return to Top-Level. Backtrace: 0: ("DEFMETHOD NO-APPLICABLE-METHOD (T)" #<#1=unused-arg> #<#1#> #<STANDARD-GENERIC-FUNCTION CLIM:STREAM-CURSOR-POSITION (2) {58BBC3B9}> (#<Two-Way Stream, Input = #<SWANK-BACKEND::SLIME-INPUT-STREAM {58B7D7B5}>, Output = #<Stream for descriptor 7>>)) 1: (CLIM-INTERNALS::INVOKE-ACCEPTING-VALUES #<Two-Way Stream, Input = #<SWANK-BACKEND::SLIME-INPUT-STREAM {58B7D7B5}>, Output = #<Stream for descriptor 7>> #<Closure Over Function (FLET #:ACCEPTING-VALUES-CONTINUATION1 CLIM-DEMO::ACCEPTING-INTERVAL) {58A68171}> :OWN-WINDOW #<unused-arg> ...) 2: (CLIM-DEMO::ACCEPTING-INTERVAL :MIN -1.0 :MAX 1.0 ...) 3: (SWANK::EVAL-REGION "(clim-demo::accepting-interval)" T) 4: ("DEFSLIMEFUN LISTENER-EVAL") _____________________TRACE WITHOUT SLIME ________________________________________ * (clim-demo::accepting-interval) No matching method for the generic function #<STANDARD-GENERIC-FUNCTION CLIM:STREAM-CURSOR-POSITION (2) {58B61979}>, when called with arguments (#<Synonym Stream to *TERMINAL-IO*>). [Condition of type PCL::NO-APPLICABLE-METHOD-ERROR] Restarts: 0: [CONTINUE] Retry call to :FUNCTION. 1: [ABORT ] Return to Top-Level. Debug (type H for help) ("DEFMETHOD NO-APPLICABLE-METHOD (T)" #<unused-arg> #<unused-arg> #<STANDARD-GENERIC-FUNCTION CLIM:STREAM-CURSOR-POSITION (2) {58B61979}> (#<Synonym Stream to *TERMINAL-IO*>)) Source: ; File: target:pcl/braid.lisp (CERROR "Retry call to ~S." 'NO-APPLICABLE-METHOD-ERROR :FUNCTION GENERIC-FUNCTION ...) 0]

4 4

[mcclim-devel] An easy question?
by Friedrich Dominicus 01 Feb '06

01 Feb '06

I'm trying to understand a bit more of clim. Now I'm stuck. How do I write an accept method which an be used in subset-completion? e.g I have the class (defclass t1 () ((val :initarg :val... (sval :initarge ...)))) Now I want to present a list of things to the user he/she can choose from something like (accept `(subset-completion ,(list (make-instance 't1 :val... (make-instance 't1 :val ....)))) I got a somewhat working solution with present-to-string but what I really want is something like this | | "(val t1 , (sval " .... for the first object | | "(val t1) .... for the second object etc. I'm sure there is something for that .... Help would be very appriciated. Regards Friedrich

1 0

[mcclim-devel] CLIM on the WEB
by Mészáros Levente 27 Jan '06

27 Jan '06

Hi, I don't know much about CLIM internals, so my theoretical question might be weird. Is it possible to render a CLIM application on current web browsers using JavaScript, XHTML and AJAX? I do not mean that is it possible right now (I wish it would be, but it certainly isn't) but conceptually? The idea comes from a requirement of being able to use light weight (actually it means already installed) clients through firewalls, etc. AFAICT some of CLIM code (event dispatch, some of event handling) would have to be (possibly automatically transformed and) run on the client side using JavaScript. Clearly a completely new backend would be needed (and I think some kind of continuation would be necessary on the server side). Maybe it's just not worth the effort... Any comments? Levy ________________________________________________________________ Pénzügyi szolgáltatás és hiteligénylés interneten keresztül a nap 24 órájában. www.klikkbank.hu

5 4

[mcclim-devel] DEFINE-APPLCATION-STARTER and a modified Clim Launcher
by Max-Gerd Retzlaff 27 Jan '06

27 Jan '06

Hello, this is a proposal for a new extension to McCLIM consisting of two parts: A general macro to produce application starter functions for McCLIM applications Most Clim application have a starter functions that just makes the application frame and afterwards runs its toplevel: (defun start () (run-frame-top-level (make-application-frame 'my-foo))) So far, so simple. But now we want a shortcut to start the toplevel in a newly created process, so we have: (defun start (&key (new-process nil)) (flet ((run () (run-frame-top-level (make-application-frame 'my-foo)))) (if new-process (clim-sys:make-process #'run :name "foo tool") (run)))) What else? Perhaps a default window width and height? A keyword parameter for the process name? . . . It has started with the first version, then someone has written the second one, that was copied by others. Further extended... Well, it has become quite convenient, and so you can find mutations of the code in the Clim Listener, Clouseau (the inspector), the Clim Launcher, Climacs, and probably others. For a strange reason all of the authors never created a simple macro for it but have copied the code literally and changed it appropriately. How unlispy! So I changed this, by making one as part of the LED Cube Modeller[1]. It basically creates the code of the second example. You can also specify a default width and height for the application frame, as well as the default process name. Then there is also the option :COMPLAIN-ABOUT-EXISTING-PROCESS; set it to T when defining the starter (the default is nil) and the generated starter function will, previously to do anything else, search for an existing process and ask what it should do about it (I wanted this behaviour for the Cube Modeller's toolbox window). In addition to this you can also specify the frame manager if you want to try out the pixie/clx-look. The new macro can be used as a drop-in replacement for e.g. the existing climacs-gui:climacs: (climi::define-application-starter climacs :function-name climacs :default-width 900 :default-height 400) For the Clim Launcher it is: (climi::define-application-starter launcher :function-name start :default-process-name "CLIM Launcher" :announce-to-clim-launcher nil) For the Clim Listener it could be: (climi::define-application-starter listener :function-name run-listener :default-width 760 :default-height 550) but there is a tiny problem with this right now that can be fixed with a small change to the Listener (more on this in a seperate mail). And finally to illustrate :COMPLAIN-ABOUT-EXISTING-PROCESS: (climi::define-application-starter toolbox :function-name start-toolbox :default-process-name "cube-modeller toolbox" :complain-about-existing-process t) For further review the expanded version of the Climacs example is attached to this mail. Still simple, but nice nevertheless as this is a quite general application starter macro, and you all know the advantage of using a macro instead of duplicating code. Clim Launcher Together with the Launcher by Dwight Holman there is an additional benefit: The macro can announce the created starter to it. So that if you use it to define the function that fires up your GUI it will automatically displayed in the Clim Launcher. As this is quite nice, I seperated my modefied version of the Clim Launcher from Clim Desktop and merged it with the DEFINE-APPLICATION-STARTER code. I propose to commit this as a new extension to the McCLIM repository itself. It's not really much code (172 lines altogether), and the barrier to use the macro should be as low as possible. If you don't want the generated function to be announced to the Launcher you can specify :ANNOUNCE-TO-CLIM-LAUNCHER as nil. The Launcher itself should not be listed for example. Or you want to use the function only internally and have your application started via another function. In this case you can announce this function manually via (add-application "Beirc" #'beirc:beirc), for example. (This is also possible if you don't want to use the macro at all, of course.) Current status The current version is work in progress. (What else?) The Clim Launcher still depends on :clim-listener, :beirc, and :closure. If we agree to merge this code with McCLIM these dependencies should be removed, and the Listener, Beirc, Climacs, etc. should instead depend on :clim-launcher (and use DEFINE-APPLICATION-STARTER or CLIM-LAUNCHER:ADD-APPLICATION). The dependency to :climacs is already removed, you might want to evaluate the above example in the package denoted by "CLIMACS-GUI" and be impressed by the fact that a "button" will automatically manifest itself in the next turn of the Launcher's command loop. Now a direct question: The macro DEFINE-APPLICATION-STARTER currently resides in the file clim-utilities.lisp together with the two functions FIND-PROCESS-WITH-NAME and DESTROY-PROCESS-WITH-NAME that it needs. These will be created in the package "CLIM-INTERNALS", which is not very nice, but on the other hand: The two functions are generally useful to interact with the threads that McCLIM provides in a portable way. (Perhaps we want them to be exported by the package "CLIM-SYS"?) And in order to use DEFINE-APPLICATION-STARTER it would be more nice to just use it as if it were part of the CLIM specification. But do we want it in the package "CLIM"? It is not part of the specification... Or should it just be in and exported by "CLIM-LAUCNHER", and everybody should :USE that package? What do you think? I'm indecisive.. Source code and a screen shot The current version of the source codeis attached to this mail. It is also in my public flux directory http://matroid.org/flux/ as clim-launcher-20060124-01.tar.bzip2 (or newer). The extracted archive is here: http://matroid.org/flux/clim-launcher/ Here is a recent screenshot of some clim applications, including Closure, Beirc, the Listener and the Launcher, Climacs, and the LED Cube Modeller (including the File Selector): http://matroid.org/flux/CLIM-Desktop-20060124-1.png (780 kB) Entertainment The first name of the macro hasn't been very nice: MAKE-RUN-GUI-DEFUN. So there has been a discussion[2] about it in #lisp. Proposals have been: DEFINE-APPLICATION-ENTRY, DEFINE-APPLICATION, DEFINE-APPLICATION-ENTRY-POINT, DEFINE-APPLICATION-ENTRY-FUNCTION, DEFINE-APPLICATION-STARTER-FUNCTION, EFINE-APPLICATION-STARTER, DEFINE-CLICKY-CLICK-THING, EFINE-APPLICATION-FIRESTARTER, DEFINE-APPLICATION-IGNITION, EFINE-DO-IT-TO-IT-FUNCTION, DEFINE-GUI-FIRE-UP-THINGIE, DEFINE-HEY-HO-LETS-GO, DEFINE-APPLICATION-INVOKER, DEFINE-APPLICATOR, DEFINE-APPLICATION-ANTI-TERMINATOR, DEFINE-APPLICATION-RUNNER, DEFINE-APPLICATION-INITIATOR, IVE-ME-AN-INITIATIR-FOR-MY-MIGHTY-GUI, AND DEFINE-APPLICATION-TOPLEVEL. Well, although I really like DEFINE-CLICKY-CLICK-THING and DEFINE-HEY-HO-LETS-GO, I hope you are okay with DEFINE-APPLICATION-STARTER. (Or is DEFINE-APPLICATION-RUNNER really better? :) ) Comments and thoughts are welcome, of course. Bye, Max Links: 1) http://blog.matroid.org/display/25 2) IRC context for the bored: http://meme.b9.com/cview.html?utime=3346791413&channel=lisp&start=334678781… PS: So many words for such a simple thing.. Hrm.. -- Max-Gerd Retzlaff <m.retzlaff(a)gmx.net> http://blog.matroid.org For your amusement: "The sixties were good to you, weren't they?" -- George Carlin

4 6

← Newer
1
...
50
51
52
53
54
55
56
...
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