May 2006 - cells-devel - mailman3.common-lisp.net

Re: [cells-devel] Celtk and SBCL (and linux)
by Ken Tilton 23 May '06

23 May '06

On 5/23/06, Frank Goenninger <frgo(a)mac.com> wrote: > > Hi all: > > Am 23.05.2006 um 21:06 schrieb Ken Tilton: > > > > > 2. find the function tk-format-now and monkey with the debug stuff > > so that any message to Tk with the word "bitmap" in it gets > > printed, and see if you can catch the output and post that. > > > > I get: > > > > tk> .f332.cv334 create bitmap 140 140 -bitmap "@\\0dev\\Celtk\ > > \x1.xbm" > > > > That works. Then changing the name to something it will not find, I > > get: > > > > Error: Tcl error: error reading bitmap file "\0dev\Celtk > > \xoxox1.xbm" > > This has to be adapted to Linux-style path names: > > "/the/path/to/the/file/1.xbm" Thanks. Pardon my OS-centrism. Like this?: (mk-bitmap :coords (list 140 140) :bitmap (conc$ "@" (namestring (make-pathname :directory '(:absolute "0dev" "Celtk") :name "x1" :type "xbm")))) kenny

2 1

[cells-devel] Re: Celtk: setting the content of a text widget ? Fileevent working !
by Frank Goenninger 21 May '06

21 May '06

Am 20.05.2006 um 20:16 schrieb Frank Goenninger: > Am 20.05.2006 um 18:24 schrieb Ken Tilton: > >> Frank Goenninger wrote: >> >>> Hi Kenny, hi all: >>> >>> I do have a text widget which is created using mk-text-widget: >>> >>> (mk-text-widget :id :receive-window >>> :state 'disabled >>> :md-value (c?n "...") >>> :height 10 >>> :width 80 >>> :borderwidth 2 >>> :relief 'sunken >>> :pady 5)) >>> >>> No matter what I do (even setting :state to 'enabled) I do get >>> anything printed in the text widget. >>> >>> I actually execute a setf on md-value of the text widget: >>> >>> (setf (md-value (fm-other :receive-window)) data) >>> >>> >>> Any idea? Thx! >> >> >> Hmmm, looks like I did not finish implementing text widgets. > > Yep, meanwhile I recognized that an observer is missing in file > entry.lisp. Well, actually I had to do (in file entry.lisp): ;; Method CLEAR: clears a text widget to zero content (defmethod clear ((self text-widget)) (tk-format `(:variable ,self) "~a delete 1.0 end" (^path))) ;; This observer puts text to the widget if md-value has been set ;; Also takes care of edge cases like initialization time and setting ;; strings of length 0... (defobserver .md-value ((self text-widget)) (trc "md-value output" self new-value) (if (or (and (not old-value) (string= new-value "")) (not new-value)) (tk-format `(:variable ,self) "~a delete 1.0 end" (^path)) (if (> (length new-value) 0) (tk-format `(:variable ,self) "~a insert end ~a" (^path) new- value)))) With this and my fileevent stuff I can now say: ;; Model for a simple terminal output window. (defmodel fileevent-test-window (window) () (:default-initargs :kids (c? (the-kids (mk-stack (:packing (c?pack-self)) (mk-label :text "Receive window" :pady 10) (mk-text-widget :id :receive-window ;:state 'disabled :md-value (c-in "") :height 10 :width 80 :borderwidth 2 :relief 'sunken :pady 5)) (mk-fileevent :id :fileevent-test :read-fn 'read-from-pipe :iostream (open "/Users/frgo/tmp/frgo-test" :direction :input)))))) ;; The method read-from-pipe reads data from a pipe generated by ;; mkfifo /Users/frgo/tmp/frgo-test and puts this as the data of a ;; text widget (defmethod read-from-pipe ((self tk-fileevent) &optional (operation :read)) (declare (ignorable operation)) (let ((stream (^iostream))) (let ((data (read-line stream nil nil nil))) (trc "*** READ-FROM-PIPE: data = " data) (when data (setf (md-value (fm-other :receive-window)) data)))) ) ;; Test function that fires up the test case (defun test-fileevent () (trc "----------------------------------------------------------------------- ------") (test-window 'fileevent-test-window) (trc "----------------------------------------------------------------------- ------") ) Now, whenever I do a $ echo "Heya this is a test" > /Users/frgo/tmp/frgo-test the text gets displayed in the window. Of course there's other uses for this: You also can open a socket and send application commands to the application. The read-from-pipe function would then be a little interpreter kicking of actions in the application... For me I put the reading function to listen to a RS232C port that is connected to an AVR-based microcontroller. The controller send status information and voltage and current values from a power supply to be displayed as info by my application... Fileevent to be put to Celtk CVS in a few days ... watch out. Frank

2 2

[cells-devel] Celtk: Not really Celtk related, but .... ?! format does unwanted optimizations ...
by Frank Goenninger 21 May '06

21 May '06

Hi all: I have that problem that I get some unwanted optimizations from format : I want to do send a string to Tcl/Tk via function tk-format-now. My call to tk-format-now looks as follows: (tk-format-now "fileevent ~A readable [list readable ~A ~A]" ch-name ch-name path)) This produces a Tcl error: Tcl error: can not find channel named "#1=file22" [Condition of type SIMPLE-ERROR] When looking at the call stack then I see the followig: 6: (CTK::TCL-EVAL-EX 25144328 "fileevent #1=file22 readable [list readable #1# .fileevent-test]") Locals: CTK::I = 25144328 CTK::S = "fileevent #1=file22 readable [list readable #1# .fileevent-test]" 7: (CTK:TK-FORMAT-NOW "fileevent ~A readable [list readable ~A ~A]" #1="file22" #1# ".fileevent-test") Locals: CTK::FMT$ = "fileevent ~A readable [list readable ~A ~A]" NIL = "file22" NIL = "file22" NIL = ".fileevent-test" Obviously Lisp optimizes the reference to the string object "file22" into a reference (Hmm - this is new to me. Is this real Lisp speak to describe the facts shown above ???). Thx for any pointers! Frank

1 0

[cells-devel] Celtk: setting the content of a text widget ?
by Frank Goenninger 20 May '06

20 May '06

Hi Kenny, hi all: I do have a text widget which is created using mk-text-widget: (mk-text-widget :id :receive-window :state 'disabled :md-value (c?n "...") :height 10 :width 80 :borderwidth 2 :relief 'sunken :pady 5)) No matter what I do (even setting :state to 'enabled) I do get anything printed in the text widget. I actually execute a setf on md-value of the text widget: (setf (md-value (fm-other :receive-window)) data) Any idea? Thx! Best wishes Frank

1 0

[cells-devel] Cells web?
by ocorrain＠yahoo.com 13 May '06

13 May '06

Hi-- I'm trying to get my head around Cells by writing an application with it, and I was wondering whether any work has been done in the area already. Has anyone used Cells as the basis for a Web app? I'm thinking specifically of something Ajax-y, with XMLHttp widget updates. Any thoughts on this line of enquiry? Tiarnán

2 1

[cells-devel] Celtk: Question on mk-entry
by Frank Goenninger 13 May '06

13 May '06

Hi again, When using the mk-entry widget I seem to not get any value back: CL-USER> (et::run-entry-test) "----------UTILSRESET----------------------------------" *** Tk_AppInit has been called. *** OBSERVER VAL: slot 'val' of ENTRY-TEST set to NIL 0> entry | "md-value output" | ENTRY | "" tk> bind . <Escape> {destroy .} 0> no event handlers for | ENTRY | |write| 0> known key | CTK::|write| | SYMBOL 0> no event handlers for | ENTRY | |write| 0> known key | CTK::|write| | SYMBOL *** OBSERVER VAL: slot 'val' of ENTRY-TEST set to 0> tcl-do-one-event-loop has left the building NIL CL-USER> In order to get this output I turned on trc output in the defobserver .mdvalue ((self entry)) method. Yet the observer does not fire. When should/does the observer fire? On each change of the entry's entry field ? I used the following code to test (also attached as a file): (defpackage :et (:use :common-lisp)) (in-package :et) (eval-when (:load-toplevel :compile-toplevel :execute) #+asdf (progn #-cells (progn (asdf:operate 'asdf:load-op :cells) (use-package :cells)) #-cl-opengl (progn (asdf:operate 'asdf:load-op :cl-openg)) #-Celtk (progn (asdf:operate 'asdf:load-op :Celtk) (use-package :Celtk)) )) (defmodel entry-test (window) ((val :accessor val :initarg :val :initform (c-in nil))) (:default-initargs :title$ "entry test" :id :entry-test :kids (c? (the-kids (mk-row (:packing (c?pack-self)) (mk-label :text "Enter value:") (mk-entry :id :frgo-entry) (mk-button-ex ("Do it !" (setf (val (fm^ :entry-test)) (md-value (fm^ :frgo-entry)))))))))) ;;; DEBUG OBSERVERS (defobserver val ((self entry-test)) (format t "~&*** OBSERVER VAL: slot 'val' of ~S set to ~A~&" self new-value)) ;;; RUN/TEST FUNCTION (defun run-entry-test () (test-window 'entry-test)) ----- The code assumes the value of the entry widget (what the user entered) is stored in md-value of the entry widget. I tried monkey style copying from the demos to no avail so far. Hmmpf! What am I doing wrong ? Thx for any hints. Frank

1 0

[cells-devel] Multiple observers for a Cell slot ?
by Frank Goenninger 11 May '06

11 May '06

Hi Kenny, hi all: While developing a library here for I/O to a microcontroller I see that I need some observers being defined to handle operations of the I/O device. Naturally I am coding these as part of the library which I plan to ship just as a compiled file. The main application also needs to define observers on some Cell slots to update the GUI and other stuff. As an observer for the slot is already defined I am denied to define another one. Now, am I doing something wrong and is is just me or maybe there should be some hook-like behavior and defobserver just adds another observer to a list of observers maintained by the Cell woodoo magic ? Thanks for comments Frank

2 1

[cells-devel] Oops, I panicked...
by Ken Tilton 04 May '06

04 May '06

I recently made a fundamental change to (setf md-slot-value) in the face of a bug in which a SETF got deferred and I could not think of a way to make the code work without taking out the integrity wrapper in (setf md-slot-value). That was dumb. The way the slot was being used (setf?! Only in eventhandlers, please.) the slot should not have been a cell. (Specify ":cell nil" in the slot definition.) What I decided to do was go the other way (more Cell-ish) and use a rule to get the slot initialized. Now I get to go back and take out the dozen extra (with-integrity (:change)...) wrappers I had to add all over the ltktest-ci demo to get that working after the dumb "fix". Anyway, if you grabbed Cells in the past few days you might want to wait till the smoke clears and grab it again. And this time I will run the Cells regression test, which I did not think to do last time. <sigh> kt

1 0