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

[cells-devel] Re: [Lisp] Rapid prototyping idea rewards crap (README)
by Ken Tilton 20 Apr '06

20 Apr '06

On 20 Apr 2006 13:40:40 -0400, Heow Eide-Goodman <lists(a)alphageeksinc.com> wrote: > > Actually Kenny, you hit it on the nose. > > Here is the process as-envisioned: > > 1. A prospective student has a gread project idea > 2. LispNYC reviews student and idea > 3. If we determine that idea and student are considered worthy, then > LispNYC says yeah or nay. > 4. (if (eq 'nay (lisp-nyc-review-process student) 'adios) (progn ... > )) > 5. We think they've got a fighting chance then LispNYC pledges $500 > 6. Student works and works and works > 7. Google reviews everything and the grants are awarded. > 8. If they're not funded by Google, then we give them the $500 > > > Since our intent is to attract smart motivated students to get a > head-start on the work rather than motivated shysters, then we should > carefully consider this. Everything comes with risks and this needs to > mitigate our risk rather than increase it. > > Please consider this, carefully. > > The RCP process is exactly the same review that we use for Google. > However, for a mere $500, it allows us: > > * More time to scrutinize the student. > * Determine whether she is sufficiently motivated to complete the > project. > * Better determine their technical chops, in Lisp or otherwise. OK, this makes no sense. Why not let Google waste their $500 instead of ours? We do the same due diligence either way, but if it turns out we screwed up, we take the hit. And I have to ask: what problem are you trying to solve? We did great last year. There was one screw-up, and I am completely to blame because I had an early warning of exactly what transpired. We have learned that lesson and will be more careful this time in the review process. But to be honest, again, I had all the early warning in the world on the cl-sockets didaster, I just sailed through that flashing red light. I thought the angle was "attract more projects". That was at least plausible. But, again, I doubt the guarantee would do that, I think it would attract (not reward) more crap. kt

1 0

[cells-devel] Re: [Lisp] Rapid prototyping idea rewards crap (README)
by Ken Tilton 20 Apr '06

20 Apr '06

On 4/20/06, Jason Scherer <jason.scherer(a)rga.com> wrote: > > > I wonder, is it legal to have one umbrella project and then have > multiple students work on different pieces of that project? Not last year. I have not looked at the rules this year. kt

1 0

[cells-devel] Celtk/Cells: How to best do own new widgets...
by Frank Goenninger 20 Apr '06

20 Apr '06

Kenny, all: some status report on my endeavor to create a hobby app with Celtk and also a few things to discuss: I have put together the GUI prototype for my app - using Tcl/Tk directly. Purpose was to learn Tcl/Tk and see how well I could do some advanced things like building my own widgets / GUI elements using only basic commands as supported by Celtk. Now there's some GUI there that can be translated straightforward to Celtk except for a meter widget for displaying analog value like voltage and current. You can test the GUI by firing it up with wish psu-rc-gui.tcl using the attached files. One is a font file that is needed to display LCD type characters (font DS-Dgital, folder ds-digital). I used the voltmeter.tcl file by Marco Maggi (http://wiki.tcl.tk/ 9109) as a reference but decided to go without actually creating a Tk widget. Now, I see the that I'd like to use some kind of new widget class either by sub-classing Celtk:widget or by enhancing the Celtk:widget class. I'd need some possibility to send over Tcl/Tk code to the wish upon first instance creation in order to install the widget on the Tk side. That's approach #1. #2 would be to do this all in Lisp and just send the drawing commands to the wish... Hmmm!? Which one would you choose. Why ? Thanks for any feedback! Cheers Frank P.S. If there's no files attached I think the cells-devel list does not allow posting attachments ... I'll send you the files if you say so.

2 2

[cells-devel] Celtk/cells: timing issue in initialization and No Widgets :-(
by Frank Goenninger 14 Apr '06

14 Apr '06

Hi Kenny and fellow I've been enhancing my power supply remote control app with some widgets to enter the RS232C/USB port name. Only issue I have is I don't see any error but no widgets appearing... Seems to be a simple one... HELP! Another, more serious thing in my eyes , is the issue I have with my different instances getting initialized. I have marked the challenging place in the code with <<< frgo: HERE - see :tk-fill ... Issue is that the object darc-rs232c-port does not seem to be finalized yet when the function darc-setup-panel gets called. So I cannot depend a text label on a cell slot of the darc-rs232c-port object... I tried to avoid this with some clumsy code but it seems simply to be wrong. Can't get my head to find another solution. Any input here of course very welcome!! Thx again! Frank ----- (in-package :cl-user) (eval-when (:load-toplevel :compile-toplevel :execute) #+asdf (progn #-cells (asdf:operate 'asdf:load-op :cells) #-Celtk (asdf:operate 'asdf:load-op :Celtk) )) (in-package :celtk-user) (defparameter *psu-rc-app* nil "The instance of the PSU Remote Control application.") ;; BASE CLASS FOR APPLICATIONS (defmodel application () (( .md-value :cell t :accessor view :initform (c-in nil) :initarg :view ) ( name :cell t :accessor name :initform (c-in nil) :initarg :name ) ( status :cell t :accessor status :initform (c- in :disabled) :initarg :status) )) ;(defmethod initialize-instance :after ((self application) &key) ; (incf (nr-instances self))) - does not work ... (defmodel application-object (family) (( .md-name :cell t :accessor id :initform (c- in :unknown) :initarg :id ))) ;; PUSHBUTTON, SIGNAL-LAMP, PUSHBUTTON-WITH-SIGNAL-LAMP MODELS (defmodel pushbutton (application-object) (( .md-value :cell t :accessor pb-state :initform (c? (if (^pressed) (on-off-toggle .cache) (initial-pb-state self))) :initarg :pb-state ) ( initial-pb-state :cell nil :initform :off :initarg :initial-pb-state :reader initial-pb-state ) ( pressed :cell :ephemeral :accessor pressed :initform (c-in nil)))) (defmacro mk-pushbutton (&rest initargs) `(make-instance 'pushbutton :fm-parent *parent* ,@initargs)) ;(defmacro push-the-button (button-id) ; `(setf (fm^v ,button-id) :pressed)) (defmodel signal-lamp (application-object) ((lamp-state :cell t :accessor lamp-state :initform (c? (if (^switched) (not .cache) (initial-lamp-state self))) :initarg :lamp-state ) ( initial-lamp-state :cell nil :initform :off :initarg :initial-lamp-state :reader initial-lamp-state ) ( switched :cell :ephemeral :accessor switched :initform (c-in nil)))) (defmacro mk-signal-lamp (&rest initargs) `(make-instance 'signal-lamp :fm-parent *parent* ,@initargs)) (defmodel pushbutton-with-signal-lamp (pushbutton signal-lamp) ()) (defmacro mk-pushbutton-with-signal-lamp (&rest initargs) `(make-instance 'pushbutton-with-signal-lamp :fm-parent *parent* ,@initargs)) ;; PSU-APP-RC MODEL (defun control-panel () (list ;; SIGNAL LAMPS ;; Mains signal lamp (mk-signal-lamp :id :mains-lamp ;:lamp-state (cr-mains-lamp-state) ) ;; OPER signal lamp (mk-signal-lamp :id :oper-lamp ;:lamp-state (cr-oper-lamp-state) ) ;; TEST signal lamp (mk-signal-lamp :id :test-lamp ;:lamp-state (cr-test-lamp-state) ) ;; FAIL signal lamp (mk-signal-lamp :id :fail-lamp ;:lamp-state (cr-fail-lamp-state) ) ;; PUSH BUTTONS AND LAMPS ;; Oper mode pushbutton with lamp (mk-pushbutton-with-signal-lamp :id :oper-mode-pb :initial-pb-state :off :lamp-state (c? (if (^pressed) (^pb-state) (initial-lamp-state self))) ) ;; Test mode pushbutton with lamp (mk-pushbutton-with-signal-lamp :id :test-mode-pb :initial-pb-state :off ;:lamp-state (c? (^pb-state)) ) ;; Ua-enable pushbutton with lamp (mk-pushbutton-with-signal-lamp :id :Ua-enable-pb :initial-pb-state :off) ;; Ug1 pushbutton with lamp (mk-pushbutton-with-signal-lamp :id :Ug1-pb :initial-pb-state :off) ;; Ug2 pushbutton with lamp (mk-pushbutton-with-signal-lamp :id :Ug2-pb :initial-pb-state :off) ;; Uh pushbutton with lamp (mk-pushbutton-with-signal-lamp :id :Uh-pb :initial-pb-state :off) ;; Uh pushbutton with lamp (mk-pushbutton-with-signal-lamp :id :Uh-pb :initial-pb-state :off) ) ) (defmodel psu-rc-app (application) ( ;; Mains status (may have several vaklues, :ok indicates OK ;-) ( mains-status :cell t :accessor mains-status :initform (c-in nil) :initarg :mains-status ) ;; Operate status: eitehr :operate-mode or :test-mode ( operate-status :cell t :accessor operate-status :initform (c- in nil) :initarg :operate-status ) ;; RS232C port ;; As soon as the port name is set try to read data from this port ;; DARC stands for Device and Application Remote Control ( darc-rs232c-port :cell t :accessor darc-rs232c-port :initform (c-in nil) :initarg :darc-rs232c-port ) ;; Voltage and current values to be displayed Units ( Ua :cell t :accessor Ua :initform (c-in nil) :initarg :Ua ) ; [ V ] ( Ia :cell t :accessor Ia :initform (c-in nil) :initarg :Ia ) ; [ A ] ( Uh :cell t :accessor Uh :initform (c-in nil) :initarg :Uh ) ; [ V ] ( Ih :cell t :accessor Ih :initform (c-in nil) :initarg :Ih ) ; [ A ] ( Ug1 :cell t :accessor Ug1 :initform (c-in nil) :initarg :Ug1 ) ; [ V ] ( Ig1 :cell t :accessor Ig1 :initform (c-in nil) :initarg :Ig1 ) ; [ mA ] ( Ug2 :cell t :accessor Ug2 :initform (c-in nil) :initarg :Ug2 ) ; [ V ] ( Ig2 :cell t :accessor Ig2 :initform (c-in nil) :initarg :Ig2 ) ; [ mA ] ) ) (defmodel rs232c-port (window) ; needs to be a widget to get a ; timer easily ;-) (( status :accessor status :cell t :initform (c-in :not-connected)) ( device-name :accessor device-name :cell t :initform (c-in nil) :initarg :device-name )) (:default-initargs :id :darc-port :timers (c? (list (make-instance 'timer :state (c-in :on) :repeat t :delay 1000 ; 1 s delay :action (lambda (timer) (declare (ignore timer)) (connect-to-darc (device-name self)))))))) (defun connect-to-darc (device-name) (when device-name (format t "~%*** Trying to connect to DARC via port ~a ...~&" device-name) ;; MISSING: Code that connects to the DARC port via USB ... ;; For now, just return NOT CONNECTED ... (values :not-connected) ) ) (defobserver status ((self rs232c-port)) (format t "~%*** Status of RS232C port ~a is now ~s.~%" (device-name self) (status self)) (when new-value (if (eq new-value :connected) (setf (state (first (timers self))) :off) (setf (state (first (timers self))) :on) ))) ;; HELPER FUNCTIONS ;; Toggles :on to :off and vice versa (defun on-off-toggle (on-or-off) (case on-or-off ( :on :off) ( :off :on ) (otherwise :off))) ; Safety ! Turn off in case of unknown value given ; (= bug in app) ... ;; PSU-RC-APP OBSERVERS (defobserver mains-status ((self psu-rc-app)) (format t "~%*** Mains-status is now ~s.~%" new-value)) (defobserver lamp-state ((self signal-lamp)) (format t "~%*** Signal lamp ~a is now ~s.~%" (id self) new-value)) (defobserver pressed ((self pushbutton)) (format t "~%*** Pushbutton ~a has been pressed (~s).~%" (id self) new-value)) (defobserver switched ((self signal-lamp)) (format t "~%*** Lamp ~a has been switched (~s).~%" (id self) new- value)) ;(defobserver pressed ((self pushbutton-with-signal-lamp)) ; (setf (switched (fm^ (md-name self)) t))) ;; Get a view / window right after making an instance ;; We only allow one instance to run ! (defmethod initialize-instance :after ((self psu-rc-app) &key) (when *psu-rc-app* (error "*** A PSU-APP-RC instance already exists. Only one allowed.")) (setq *psu-rc-app* self) (setf (view self) (make-instance 'psu-rc-app-view)) (setf (darc-rs232c-port self) (make-instance 'rs232c-port))) ;; PSU-RC-APP-VIEW - the view/GUI for the PSU Remote Control Application (defmodel psu-rc-app-view (window) ((selected-oper-pb :cell :ephemeral :accessor selected-oper-pb :initform (c-in nil) :initarg :selected-oper-pb) (selected-test-pb :cell :ephemeral :accessor selected-test-pb :initform (c-in nil) :initarg :selected-test-pb)) (:default-initargs :id :psu-rc-app-view :kids (c? (the-kids (app-menubar) (control-panel) (darc-setup-panel) )))) ;(defmethod initialize-instance :after ((self psu-rc-app-view) &key) ; (tk-format '(:configure "title") "wm title . ~a" (slot-value self 'title$))) (defobserver title$ ((self window)) (tk-format '(:configure "title") "wm title . ~a" (or new-value "Untitled"))) (defun app-menubar () (mk-menubar :id :psu-rc-menu-bar :kids (c? (the-kids (mk-menu-entry-cascade-ex (:label "File") (mk-menu-entry-command :label "Quit" :command "exit")) (mk-menu-entry-cascade-ex (:label "Operate") (mk-menu-entry-command :label "Set Mains Status to :OK" :command (c? (tk-callback .tkw 'set-mains-ok (lambda () (setf (mains-status *psu-rc-app*) :ok))))) (mk-menu-entry-command :label "Action: Push the OPER MODE button" :command (c? (tk-callback .tkw 'push-oper- mode-pb (lambda () (setf (pressed (fm^ :oper-mode-pb)) t)))) ) ) ) ) ) ) (defun darc-setup-panel () (mk-stack () (mk-row () (mk-label :text "DARC RS232C Port Device Name:") (mk-entry :id :darc-port-device-name :md-value (c-in "") :background "grey")) (mk-row () (mk-label :text "DARC Connect Status:") (mk-canvas ;; <<< frgo: HERE - see :tk-fill ... :height 40 :width 40 :kids (c? (the-kids (mk-rectangle :coords '(0 0 40 40) :tk-fill (c? (if (eq (if (darc-rs232c-port *psu-rc-app*) (status (darc-rs232c-port *psu-rc-app*)) nil) :connected) "green" "red"))))))) (mk-row () (mk-label :text (c? (if (darc-rs232c-port *psu-rc-app*) (status (darc-rs232c-port *psu-rc-app*)) "")) :relief 'sunken)))) ;; (defmodel main-controls-view (canvas) ;; () ;; (:default-initargs ;; :id :main-controls-view ;; :kids (c? (the-kids ;; ( (defun run-psu-rc-app () (cells-reset 'tk-user-queue-handler) (tk-test-class 'psu-rc-app))

2 4

[cells-devel] Celtk/cells: No Widgets! Help!
by Frank Goenninger 14 Apr '06

14 Apr '06

Hi again ... With substantial help I was able to get some more stuff to work as expected. Now I am struggling with the fact that the menubar does indeed have the menus I installed but the few widgets I placed into the window simply don't appear... Hmm - well, yes, why?? (As always, there's a FRGO placed here and there) How do I debug what is being sent to wish ? Thx for any inputs. Frank --- ;; -*- mode: Lisp; Syntax: Common-Lisp; Package: celtk-user; -*- (in-package :cl-user) (eval-when (:load-toplevel :compile-toplevel :execute) #+asdf (progn #-cells (asdf:operate 'asdf:load-op :cells) #-Celtk (asdf:operate 'asdf:load-op :Celtk) )) (in-package :celtk-user) (defparameter *psu-rc-app* nil "The instance of the PSU Remote Control application.") ;; BASE CLASS FOR APPLICATIONS (defmodel application () (( .md-value :cell t :accessor view :initform (c-in nil) :initarg :view ) ( name :cell t :accessor name :initform (c-in nil) :initarg :name ) ( status :cell t :accessor status :initform (c- in :disabled) :initarg :status) )) ;(defmethod initialize-instance :after ((self application) &key) ; (incf (nr-instances self))) - does not work ... (defmodel application-object (family) (( .md-name :cell t :accessor id :initform (c- in :unknown) :initarg :id ))) ;; PUSHBUTTON, SIGNAL-LAMP, PUSHBUTTON-WITH-SIGNAL-LAMP MODELS (defmodel pushbutton (application-object) (( .md-value :cell t :accessor pb-state :initform (c? (if (^pressed) (on-off-toggle .cache) (initial-pb-state self))) :initarg :pb-state ) ( initial-pb-state :cell nil :initform :off :initarg :initial-pb-state :reader initial-pb-state ) ( pressed :cell :ephemeral :accessor pressed :initform (c-in nil)))) (defmacro mk-pushbutton (&rest initargs) `(make-instance 'pushbutton :fm-parent *parent* ,@initargs)) ;(defmacro push-the-button (button-id) ; `(setf (fm^v ,button-id) :pressed)) (defmodel signal-lamp (application-object) ((lamp-state :cell t :accessor lamp-state :initform (c? (if (^switched) (not .cache) (initial-lamp-state self))) :initarg :lamp-state ) ( initial-lamp-state :cell nil :initform :off :initarg :initial-lamp-state :reader initial-lamp-state ) ( switched :cell :ephemeral :accessor switched :initform (c-in nil)))) (defmacro mk-signal-lamp (&rest initargs) `(make-instance 'signal-lamp :fm-parent *parent* ,@initargs)) (defmodel pushbutton-with-signal-lamp (pushbutton signal-lamp) ()) (defmacro mk-pushbutton-with-signal-lamp (&rest initargs) `(make-instance 'pushbutton-with-signal-lamp :fm-parent *parent* ,@initargs)) ;; PSU-APP-RC MODEL (defun control-panel () (list ;; SIGNAL LAMPS ;; Mains signal lamp (mk-signal-lamp :id :mains-lamp ;:lamp-state (cr-mains-lamp-state) ) ;; OPER signal lamp (mk-signal-lamp :id :oper-lamp ;:lamp-state (cr-oper-lamp-state) ) ;; TEST signal lamp (mk-signal-lamp :id :test-lamp ;:lamp-state (cr-test-lamp-state) ) ;; FAIL signal lamp (mk-signal-lamp :id :fail-lamp ;:lamp-state (cr-fail-lamp-state) ) ;; PUSH BUTTONS AND LAMPS ;; Oper mode pushbutton with lamp (mk-pushbutton-with-signal-lamp :id :oper-mode-pb :initial-pb-state :off :lamp-state (c? (if (^pressed) (^pb-state) (initial-lamp-state self))) ) ;; Test mode pushbutton with lamp (mk-pushbutton-with-signal-lamp :id :test-mode-pb :initial-pb-state :off ;:lamp-state (c? (^pb-state)) ) ;; Ua-enable pushbutton with lamp (mk-pushbutton-with-signal-lamp :id :Ua-enable-pb :initial-pb-state :off) ;; Ug1 pushbutton with lamp (mk-pushbutton-with-signal-lamp :id :Ug1-pb :initial-pb-state :off) ;; Ug2 pushbutton with lamp (mk-pushbutton-with-signal-lamp :id :Ug2-pb :initial-pb-state :off) ;; Uh pushbutton with lamp (mk-pushbutton-with-signal-lamp :id :Uh-pb :initial-pb-state :off) ;; Uh pushbutton with lamp (mk-pushbutton-with-signal-lamp :id :Uh-pb :initial-pb-state :off) ) ) (defmodel psu-rc-app (application) ( ;; Mains status (may have several vaklues, :ok indicates OK ;-) ( mains-status :cell t :accessor mains-status :initform (c-in nil) :initarg :mains-status ) ;; Operate status: eitehr :operate-mode or :test-mode ( operate-status :cell t :accessor operate-status :initform (c- in nil) :initarg :operate-status ) ;; RS232C port ;; As soon as the port name is set try to read data from this port ;; DARC stands for Device and Application Remote Control ( darc-rs232c-port :cell t :accessor darc-rs232c-port :initform (c-in nil) :initarg :darc-rs232c-port ) ;; Voltage and current values to be displayed Units ( Ua :cell t :accessor Ua :initform (c-in nil) :initarg :Ua ) ; [ V ] ( Ia :cell t :accessor Ia :initform (c-in nil) :initarg :Ia ) ; [ A ] ( Uh :cell t :accessor Uh :initform (c-in nil) :initarg :Uh ) ; [ V ] ( Ih :cell t :accessor Ih :initform (c-in nil) :initarg :Ih ) ; [ A ] ( Ug1 :cell t :accessor Ug1 :initform (c-in nil) :initarg :Ug1 ) ; [ V ] ( Ig1 :cell t :accessor Ig1 :initform (c-in nil) :initarg :Ig1 ) ; [ mA ] ( Ug2 :cell t :accessor Ug2 :initform (c-in nil) :initarg :Ug2 ) ; [ V ] ( Ig2 :cell t :accessor Ig2 :initform (c-in nil) :initarg :Ig2 ) ; [ mA ] ) ) (defmodel rs232c-port (window) ; needs to be a widget to get a ; timer easily ;-) (( status :accessor status :cell t :initform (c-in :not-connected)) ( device-name :accessor device-name :cell t :initform (c-in nil) :initarg :device-name )) (:default-initargs :id :darc-port :timers (c? (list (make-instance 'timer :state (c-in :off) :repeat t :delay 10000 ; 10 s delay :action (lambda (timer) (declare (ignore timer)) (let ((status (status (darc-rs232c-port *psu-rc-app*))) (device-name (device-name (darc-rs232c-port *psu-rc-app*)))) (if (and (eq status :not-connected) device-name ) (connect-to-darc device-name))))))))) (defun connect-to-darc (device-name) (format t "~%*** connect-to-darc been called for port ~a ...~&" device-name) (when device-name (format t "~%*** Trying to connect to DARC via port ~a ...~&" device-name) ;; Missing: Code that connects to the DARC port via USB ... ;; For now, just return NOT CONNECTED ... :not-connected ) ) (defobserver status ((self rs232c-port)) (format t "~%*** Status of RS232C port ~a is now ~s.~%" (device-name self) (status self)) (when new-value (if (eq new-value :connected) (setf (state (first (timers self))) :off) (setf (state (first (timers self))) :on) ))) ;; HELPER FUNCTIONS ;; Toggles :on to :off and vice versa (defun on-off-toggle (on-or-off) (case on-or-off ( :on :off) ( :off :on ) (otherwise :off))) ; Safety ! Turn off in case of unknown value given ; (= bug in app) ... ;; PSU-RC-APP OBSERVERS (defobserver mains-status ((self psu-rc-app)) (format t "~%*** Mains-status is now ~s.~%" new-value)) (defobserver lamp-state ((self signal-lamp)) (format t "~%*** Signal lamp ~a is now ~s.~%" (id self) new-value)) (defobserver pressed ((self pushbutton)) (format t "~%*** Pushbutton ~a has been pressed (~s).~%" (id self) new-value)) (defobserver switched ((self signal-lamp)) (format t "~%*** Lamp ~a has been switched (~s).~%" (id self) new- value)) ;(defobserver pressed ((self pushbutton-with-signal-lamp)) ; (setf (switched (fm^ (md-name self)) t))) ;; Get a view / window right after making an instance ;; We only allow one instance to run ! (defmethod initialize-instance :after ((self psu-rc-app) &key) (when *psu-rc-app* (error "*** A PSU-APP-RC instance already exists. Only one allowed.")) (setq *psu-rc-app* self) (setf (view self) (make-instance 'psu-rc-app-view)) (setf (darc-rs232c-port self) (make-instance 'rs232c-port))) ;; PSU-RC-APP-VIEW - the view/GUI for the PSU Remote Control Application (defmodel psu-rc-app-view (window) ((selected-oper-pb :cell :ephemeral :accessor selected-oper-pb :initform (c-in nil) :initarg :selected-oper-pb) (selected-test-pb :cell :ephemeral :accessor selected-test-pb :initform (c-in nil) :initarg :selected-test-pb)) (:default-initargs :id :psu-rc-app-view :kids (c? (the-kids (app-menubar) (control-panel) (darc-setup-panel) )))) ;(defmethod initialize-instance :after ((self psu-rc-app-view) &key) ; (tk-format '(:configure "title") "wm title . ~a" (slot-value self 'title$))) (defobserver title$ ((self window)) (tk-format '(:configure "title") "wm title . ~a" (or new-value "Untitled"))) (defun app-menubar () (mk-menubar :id :psu-rc-menu-bar :kids (c? (the-kids (mk-menu-entry-cascade-ex (:label "File") (mk-menu-entry-command :label "Quit" :command "exit")) (mk-menu-entry-cascade-ex (:label "Operate") (mk-menu-entry-command :label "Set Mains Status to :OK" :command (c? (tk-callback .tkw 'set-mains-ok (lambda () (setf (mains-status *psu-rc-app*) :ok))))) (mk-menu-entry-command :label "Action: Push the OPER MODE button" :command (c? (tk-callback .tkw 'push-oper- mode-pb (lambda () (setf (pressed (fm^ :oper-mode-pb)) t)))) ) ) ) ) ) ) (defun darc-setup-panel () ; <<< frgo: HERE (mk-stack () (mk-row () (mk-label :text "DARC RS232C Port Device Name:") (mk-entry :id :darc-port-device-name :md-value (c-in "") :background "grey")) (mk-row () (mk-label :text "DARC Connect Status:") (mk-canvas ;; :height 40 :width 40 :kids (c? (the-kids (mk-rectangle :coords '(0 0 40 40) :tk-fill (c? (if (eq (if (darc-rs232c-port *psu-rc-app*) (status (darc-rs232c-port *psu-rc-app*)) nil) :connected) "green" "red"))))))) (mk-row () (mk-label :text (c? (if (darc-rs232c-port *psu-rc-app*) (status (darc-rs232c-port *psu-rc-app*)) "")) :relief 'sunken)))) (defun run-psu-rc-app () (cells-reset 'tk-user-queue-handler) (tk-test-class 'psu-rc-app))

3 4

[cells-devel] Re: Celtk/Cells: Need a little help...
by Frank Goenninger 12 Apr '06

12 Apr '06

Am 12.04.2006 um 22:26 schrieb Ken Tilton: > >> >> (setf (pb-state (fm^ :oper-mode-pb)) ;; FRGO: >> HERE !!! >> (on-off-toggle >> (fm^v :oper-mode-pb)))))) ;; FRGO: >> HERE !!! > > > (mk-menu-entry-command > :label "Action: Push the OPER MODE button" > :command (c? (tk-callback .tkw 'push-oper- > mode-pb > (lambda () > (setf (fm^v :oper-mode-pb) ;; FRGO: HERE !!! > (on-off-toggle > (fm^v :oper-mode-pb)))))) ;; FRGO: > HERE !!! > ) > > We have three slots in play now: .md-value, enabled, and pb- > state. .md-value because fm^v expands to (md-value (fm^ ...)) > > As the ltktest-cells-inside doc says, I like to use the slot md- > value of an instance the same way TK treats the name of an instance > as a variable, namely to hold the key value that instance > represents in the application. > > It is not clear to me that enabled is that slot, even tho you have > the pb-state initarg associated with it. I would think that pb- > state is currently playing the key role of holding the key on/off > value. This is confirmed by you setting the toggle result into pb- > state. > > On the other hand, I see pb-state is ephemeral. I also see: > > (defmacro push-the-button (button-id) > `(setf (fm^v ,button-id) :pressed)) > > Now there you are setting the md-value to :pressed, but since I see > toggle intentions, I am guessing this is a button that gets pressed > and then released then pressed again, and the second time produces > the opposite value as the first. So, putting it all together (and > throwing out altogether enabled since I see that is not yet > implemented): > > (defmodel pushbutton (application-object) > ((.md-value :cell t :accessor pb-state :initform (c-in :off)))) > > (mk-menu-entry-command > :label "Action: Push the OPER MODE button" > :command (c? (tk-callback .tkw 'push-oper-mode-pb > (lambda () > (setf (fm^v :oper-mode-pb) > (on-off-toggle > (fm^v :oper-mode-pb))))))) > > If you want to get a little fancier: > > (defmodel pushbutton (application-object) > ((.md-value :cell t :accessor pb-state > :initform (c? (if (^pressed) > (on-off-toggle .cache) > (initial-pb-state self)))) > (pressed :cell :ephemeral :intiform (c-in nil) ... etc) > (initial-pb-state :cell nil ....etc ))) > > (mk-menu-entry-command > :label "Action: Push the OPER MODE button" > :command (c? (tk-callback .tkw 'push-oper-mode-pb > (lambda () > (setf (pressed (fm^ :oper-mode-pb)) t))))) > > The latter can be good for doing things like associating a click > sound with the button press, because then you just have other cells > watching (^pressed). Otherwise you end up loading more and more > code into the menu callback. > > hth, ken You wonder if this helps? You just not only discovered some bugs but also explained to me .cache and real use of .md-value ... It certainly helps!! Thanks so much. Frank

1 0

Re: [cells-devel] initial stab at using Cells
by Ken Tilton 11 Apr '06

11 Apr '06

On 4/10/06, Jack Unrue <jdunrue(a)gmail.com> wrote: > > I feel the need to strike the right balance between UI/logic separation > vs. taking full advantage of Cells. Oh, if you are big on separation maybe you can confirm something I suspect, namely that Cells, by allowing different instances of the same class to have different rules for the same slot, makes OO design. For example, one can have a game normally look like: (make-instance 'game :speed (c? (* (^difficulty-slider) 500))... But then for debugging a hard problem you might want to play back a log at full speed and so the replay code goes: (make-instance 'game :speed 500... In the first case the game /instance/ is being driven by the GUI slider widget, but the game /class/ does not know about the GUI. Does that make sense in resolving the separation issue? ken

2 2

[cells-devel] initial stab at using Cells
by Jack Unrue 10 Apr '06

10 Apr '06

Well, I've gotten through my first round of experimenting with Cells, and I have to say I like it a lot. If you want to see some code, take a look at: http://common-lisp.net/websvn/filedetails.php?repname=graphic-forms&path=%2… which is the data model for a simple game where you click on blocks to score points (and where the remaining blocks fall down to fill in the hole(s)). The game gets progressively harder as you pass from one level to the next. The UI displays the current level, current score, and points needed for the next level. Screenshot here: http://sourceforge.net/project/screenshots.php?group_id=163034&ssid=31548 If you look at the model, there is a shape-data slot that really ought to be ephemeral based on how the score slot's formula depends on it (the 'shape' score should only be added to the overall score tally once, no matter how many times the UI asks for the score). But I was seeing some intermittent behavior where it seemed like the shape-data value had already been propagated (and thus cleared) by the time that my UI code asked for the score. So I took the :ephemeral attribute off until I get some more time to figure that out. I'm sure this is a bug in my understanding, not in Cells. It would be good to document some typical strategies for dealing with self-referential slots (circularity) but in thinking about how I would describe what I did, I can see how it would be hard to explain to someone else :-) -- Jack Unrue

2 3

[cells-devel] tiny patch for running Cells 3 on CLISP
by Jack Unrue 09 Apr '06

09 Apr '06

Hello Kenny, As of CLISP 2.38 (if not earlier, I haven't checked), the #+clisp defun for slot-definition-name is no longer necessary. With that commented out, motor-control.lisp runs fine. Just thought you'd like to know :-) I'm starting to look at Cells 3 with my first experiment being to write a simple game as a demo for my Graphic-Forms project, using Cells as the data model of course. I'll let you know how it goes. -- Jack Unrue

2 3

[cells-devel] Celtk on ACL80 running on an MacBook Pro ...
by Frank Goenninger 07 Apr '06

07 Apr '06

Kenny, fellow Cells Users, Just to show that in you can do it principle here's a screenshot showing the result of running Celtk / Cells kicked off by (ctk::tk- test) in AllegroCL 8.0 on my brand new MacBook Pro ... Of course, there's other apps available also ;-) Have fun - and yes, ACL is running sloooooowww ... (Rosetta obviously keeping both cores of the Intel CPU busy at 80% load level ...) Frank

2 1

[cells-devel] Re: Celtk/Cells3 declarative, dataflow paradigm contrasted with Ltk/imperative paradigm
by Ken Tilton 05 Apr '06

05 Apr '06

John, Sorry, it was late, I reacted too hastily. That error message looks wild, not sure what to make of it. Unfortunately, I have no Linux system. But the original developers of LTk use Linux and are looking at Celtk these days. I have not heard from them, but a query on the cells-devel mailing list might turn up someone using both Linux and Celtk. Otherwise, it might helpt to track down tk-format-now and tweak it so that the branch to display messages sent to Tk always fires, then see (a) if those messages look okay (post them to cells-devel) and (b) how far you get before Celtk dies. kt On 4/5/06, John Landahl <john(a)landahl.org> wrote: > > > Right at the top of ltktest-cells-inside.lisp you will find: > > > > #+test-ltktest > > (progn > > (cells-reset 'tk-user-queue-handler) > > ; ...huge comment elided.... > > (tk-test-class 'ltktest-cells-inside)) > > Yep, saw that, and I suppose I expected that loading celtk would set > test-ltktest. Removing the #+ and re-evaluating does startup the > test. > > However, the result is a bunch of errors and a big traceback. Here's > what looks like the most useful chunk: > > 0> numparse | :=> 42read-data:UNKNOWNcolor name "systembuttonface" > > read-data:INVALIDcommand name ".cv-scroller.test-canvas" > > > INVALIDCOMMANDNAME.cv-scroller.test-canvasUNKNOWNCOLORNAMEsystembuttonfaceBADWINDOWPATHNAME.cv-scroller.test-canvasINVALIDCOMMANDNAME.cv-scroller.test-canvas.bkg-popINVALIDCOMMANDNAME.cv-scroller.test-canvas.bkg-popINVALIDCOMMANDNAME.cv-scroller.test-canvas.bkg-popINVALIDCOMMANDNAME.cv-scroller.test-canvas.bkg-popCANREAD.cv-scroller.test-canvas.bkg-pop.bkg > An error of type READER-ERROR has occured: READER-ERROR on > #<TWO-WAY-STREAM > :INPUT-STREAM > #<SB-SYS:FD-STREAM for "descriptor 14" {A755EC9}> > > :OUTPUT-STREAM #<SB-SYS:FD-STREAM for "descriptor 13" {A755541}>>: > illegal terminating character after a colon: #\ > 0: (SB-DEBUG:BACKTRACE > 536870911 > #<SB-SYS:FD-STREAM for "a constant string" {AFCDB01}>) > 1: (LTK::TRIVIAL-DEBUGGER #<READER-ERROR {AA34AF1}> #<unavailable > argument>) > 2: (INVOKE-DEBUGGER #<READER-ERROR {AA34AF1}>) > 3: (ERROR READER-ERROR) > 4: (SB-IMPL::%READER-ERROR > #<TWO-WAY-STREAM > :INPUT-STREAM #<SB-SYS:FD-STREAM for "descriptor 14" {A755EC9}> > :OUTPUT-STREAM #<SB-SYS:FD-STREAM for "descriptor 13" {A755541}>> > "illegal terminating character after a colon: ~S") > 5: (SB-IMPL::READ-TOKEN > #<TWO-WAY-STREAM > :INPUT-STREAM #<SB-SYS:FD-STREAM for "descriptor 14" {A755EC9}> > :OUTPUT-STREAM #<SB-SYS:FD-STREAM for "descriptor 13" {A755541}>> > #\:) > 6: (READ-PRESERVING-WHITESPACE > #<TWO-WAY-STREAM > :INPUT-STREAM #<SB-SYS:FD-STREAM for "descriptor 14" {A755EC9}> > :OUTPUT-STREAM #<SB-SYS:FD-STREAM for "descriptor 13" {A755541}>> > NIL > NIL > T) > 7: (READ-PRESERVING-WHITESPACE > #<TWO-WAY-STREAM > :INPUT-STREAM #<SB-SYS:FD-STREAM for "descriptor 14" {A755EC9}> > :OUTPUT-STREAM #<SB-SYS:FD-STREAM for "descriptor 13" {A755541}>> > NIL > NIL > NIL) > 8: (LTK::MAIN-ITERATION :BLOCKING T) > 9: ((LAMBDA ())) > 10: ((LABELS LTK::USE-DEBUGGER) > #<FUNCTION LTK::TRIVIAL-DEBUGGER> > #<CLOSURE (LAMBDA #) {AA3477D}>) > 11: (LTK:MAINLOOP :SERVE-EVENT NIL) > > I'm running SBCL 0.9.11 on Linux, if it matters. My Tk version is > 8.4. > > > No, but do compare it to 'ltktest-cells-inside to get a feel for how > > Cells transforms development. > > I definitely will. I'd very much like to do more declarative > programming where it makes sense, and (as you and others have pointed > out) UIs are a natural fit. So it will be good to compare your > approach to the more usual (less intelligent) approach. > -- > John Landahl <john(a)landahl.org> > http://landahl.org/john >

1 1

[cells-devel] Re: Cells: How to later set a formula for a cell ?
by Ken Tilton 03 Apr '06

03 Apr '06

Goenninger, Frank wrote: > Hi Kenny, > > currently heavily playing wit Celtk... > > I have up to now only set a cell's formula by using directly (c? ...) > with default-initargs. Now I am stopped cold by the fact that I have > to be able to set the formula by some setf form. How to do that in a > conforming way ? Download KR from the Garnet system, they have a million backdoors like that. :) What's the big picture on this? Maybe there is a way to do it without an alley-oop. If you sell me on the need, and you can at least start the slot as c-input, I imagine there is some way to do this. If you do not sell me on the need, I will still give you some pointers* on how to mess up the beauty of Cells yourself.:) But I think you will still need to start with a c-input, or you will lose the dependencies (Cells does not record dependencies on slots not mediated by Cells.) ken (going out for groceries soon) * Look at c-install, md-awaken, c-awaken-cell, and their neighbors.

2 2

Re: [cells-devel] Celtk: How to set title of Wish window and also name of app ?
by Ken Tilton 03 Apr '06

03 Apr '06

Frank Goenninger wrote: > Another question: > > Am 02.04.2006 um 06:12 schrieb Ken Tilton: > >> Goenninger, Frank wrote: >> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA512 >>> >>> Hi Kenny and all others: >>> >>> I do have the following mini app now: >>> >>> - -x-x-x-x-x- >>> >>> (defmodel psu-rc-app (window) >>> () >>> (:default-initargs >>> :id :psu-rc-app-w >>> :title$ "System Power Supply Remote Control (Version A.01.00)" >>> :kids (c? (the-kids >>> (app-menubar))))) >> > > Why does the title not get set via this default-initargs statement ? This is the same story: I just have not done anything yet to handle the window class itself. Background: If you expand any of the (deftk <widget>...) forms (actually, I strongly recommend you do that and stare at /all/ the varieties of code) you will see they expand into quite a bit of code, including a (defobserver <config parameter> ...) for every slot/tk config parameter. The way Celtk (and Cells-Gtk) work is that CLOS classes are defined for every TK widget type. A CLOS slot is defined for every tk config parameter. So with widgets you just set the corresponding CLOS instance slot and a defobserver sends that to Tk via: "<widget> configure -<config param name> <value from CLOS slot>". I just need to do for the window class what I did with all the widgets and canvas items (the other job deftk handles). What title$ needs is: (defobserver title$ ((self window)) (tk-format '(:configure "title") "wm title . ~s" (or new-value "Untitled"))) As I look at the other "wm..." commands I can see I first need to add some slots to the window class and then for each a defobserver to shoot the value across to Tk on any change. [Side note: if you track down the mechanism by which make-instance leads to a corresponding TK widget creation, you will find some code that sweeps throug all the slots populated at make-instance time and includes thos config options in the widget creation. Which is why the generated defobservers check for old-value-boundp; the first time the observer gets invoked (the only time old-value-boundp is nil) is during make-instance, and the observer need not do anything since make-instance (eventually) gets the configs across in the widget creation command. > > And another one: > > I see there is the title$ slot of a window. How do I setf this > correctly ? > The following does not work: > > (setf (title$ (fm^ :psi-rc-app-w)) "my new title") > > It (of course) emits an error that title$ is not a valid function - > yes, no, ahem, what? why? I am not sure I have the same code you have, since I have already changed that slot's initform thus: (title$ :initarg :title$ :accessor title$ :initform (c? (string-capitalize (class-name (class-of self))))) So your error could be for two reasons. Either I originally coded it thus (title$ :reader title$....) thinking the title$ would never change, which is nonsense because a doc window starts out "Untitled" and then that changes when they save. Anyway, if I do not tell CLOS to create a writer it will not do so. Simple. But I doubt I specified just "reader". More likely (because even i can see it on the current code base) title$ is not exported and you are playing around in celtk-user, as I did deliberately to find out which symbols need to be exported. So just add title$ to the symbols exported from the defpackage :celtk form. > > Thanks for some help here., The greater help I can offer is what I do when I cannot believe my eyes on an error: (apropos "title$"), though we both use AllegrroCL so we get to use the groovy Apropos dialog. That not only shows you if a symbol is exported, it will show you if there is a setf as well as a reader. In a case like yours where you have already compiled code and it has failed, you will see the symbol title$ in both the celtk and celtk-user packages. That is a tip-off that the celtk symbol was not exported, because had it been the compiler would not have interned a new symbol in celtk-user when it got to the reference to title$. kt

1 1

[Fwd: Re: [cells-devel] Celtk: How to set title of Wish window and also name of app ?]
by Ken Tilton 02 Apr '06

02 Apr '06

-------- Original Message -------- Subject: Re: [cells-devel] Celtk: How to set title of Wish window and also name of app ? Date: Sat, 01 Apr 2006 23:12:23 -0500 From: Ken Tilton <kentilton(a)gmail.com> Reply-To: kentilton(a)gmail.com To: Goenninger, Frank <fgoenninger(a)prion.de> References: <F43CECE8-7EFF-46B9-A4AA-106AA92E3265(a)prion.de> Goenninger, Frank wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA512 > >Hi Kenny and all others: > >I do have the following mini app now: > >- -x-x-x-x-x- > >(defmodel psu-rc-app (window) > () > (:default-initargs > :id :psu-rc-app-w > :title$ "System Power Supply Remote Control (Version A.01.00)" > :kids (c? (the-kids > (app-menubar))))) > >;; THIS IS HOW I SET THE TITLE OF THE WISH SHELL WINDOW >;; Any better way? > >(defmethod initialize-instance :after ((self psu-rc-app) &key) > (tk-format '(:configure "title") "wm title . HI")) > > Yes and no. No in that, no, there is not a better way. :) Yes in that there should be. :) Since there is only one Tk class like this, a fancy macro might not have much value. What we need is a bunch of: (defobserver title$ ((self window)) (tk-format '(:configure "title") "wm title . ~a" (or new-value "Untitled"))) ...observers, one per "wm XXXX...." that might follow from a window attribute. Note that, unlike intervening during i-i, this works even on /changes/ to the title (which would be unusual, but for other window attributes perfectly normal. so let's hand;e the general case. Also... no, sorry, i forgot myself: the ii call to tk-format gets deferred until the tk-client-que-handler decides to dispatch configures, which is after things get made, so the window has been instantiated on the TK side before the tile change gets dispatched. Anyway, if someone wants to code up the observers I will happily add them to Celtk, if not I will certainly get to them eventually as my need arises. Right now I am going quietly mad trying to make sense of Tcl/Tk handling of fonts and text items in a canvas. :) As for the application name, er, can you copy wish.exe to frank.exe? Otherwise, if the doc does not help, I would try comp.lang.tcl. But if there is anyway to control that, I imagine we can get Celtk to handle it. ken

1 1

[cells-devel] Celtk: How to set title of Wish window and also name of app ?
by Goenninger, Frank 02 Apr '06

02 Apr '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi Kenny and all others: I do have the following mini app now: - -x-x-x-x-x- (defmodel psu-rc-app (window) () (:default-initargs :id :psu-rc-app-w :title$ "System Power Supply Remote Control (Version A.01.00)" :kids (c? (the-kids (app-menubar))))) ;; THIS IS HOW I SET THE TITLE OF THE WISH SHELL WINDOW ;; Any better way? (defmethod initialize-instance :after ((self psu-rc-app) &key) (tk-format '(:configure "title") "wm title . HI")) (defun app-menubar () (mk-menubar :id :psu-rc-menu-bar :kids (c? (the-kids (mk-menu-entry-cascade-ex (:label "File") (mk-menu-entry-separator) (mk-menu-entry-command :label "Quit" :command "exit")))))) (defun run-psu-rc-app () (cells-reset 'tk-user-queue-handler) (tk-test-class 'psu-rc-app)) - -x-x-x-x-x- Hmm - now I wonder if this is really the right way to set the title of the window ... Next question: On the Mac there is the Application name displayed in the top left corner when an app gets activated. This always says "Wish" which is something I want to set to the my own application name .. Purely a Mac and Tcl/Tk problem but ... Thanks for any feedback. Cheers! Frank -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.0.5 (Build 5050) iQIVAwUBRC8m8GAKVUddnkqnAQpQhA/9GkwObg42wTUXiS2faUVNEqP57/nS2OqF ++7HRu2s2NCGvanLRCoJZOMVXrsasHE0K7izLCuMJAqF67YDr6UsO8EOJVkPHWIg ogb6nc5FYO/pAR2MzbuH00JUURs4VSNTc61bC+JV47kzlkt5Uzx1BMNOWZoNWrUs lPWanXxDNcmlbPmSY6Jz252/kzR3jyGlbQViBqZtPNkkrCuip8Bs39VBqr4iaQRR LVMisvjas/is3KbBIVlAyLpX2gBvEivPa+oXfTmnG0rWUbfkYKms7EUT9uwWhxVG TOTP/8eZkFinPtObs/8hUcKNDSPs/4rAzPvH75ioOGZGkM2yAeNC6rTbOgyDvOvh bEBGhO20e064CmowKfbqZNFBHwmCtVvMopFhSMeaFEwBMPqjutAyWQ0F8/CXd121 BeA6ARRwi80q/hXPy38n80udY6XPkgNlNp7WAKIIoyiqZuaC9TMgik0t+W6WKdnq qrm1sZ4arT6tkzoBrobShZAk4pTl+k4ukB0wXIhwPPOUHR/mzPJzOKnkEFNtsAXi b1oF9A6deu8dB25HOv+aNRF6yUUAwf8eUvBhCpIGkfyjP6/hw2h56bgyPkmriH8Y 58BeT8tEoxNQhmoDryWbIRFgIVGjRw1d4D5yo8I6xeXmPXitGymaIDs9AVu9srhp shYQCEvr3NA= =+dKG -----END PGP SIGNATURE-----

1 0