October 2005 - cells-gtk-cvs@common-lisp.net

[cells-gtk-cvs] CVS update: root/gtk-ffi/gtk-adds.c
by pdenno＠common-lisp.net 08 Oct '05

08 Oct '05

Update of /project/cells-gtk/cvsroot/root/gtk-ffi In directory common-lisp.net:/tmp/cvs-serv15143/root/gtk-ffi Modified Files: gtk-adds.c Log Message: Added stuff for DrawingArea and GdkColor Date: Sat Oct 8 16:43:37 2005 Author: pdenno Index: root/gtk-ffi/gtk-adds.c diff -u root/gtk-ffi/gtk-adds.c:1.3 root/gtk-ffi/gtk-adds.c:1.4 --- root/gtk-ffi/gtk-adds.c:1.3 Sun May 29 23:16:56 2005 +++ root/gtk-ffi/gtk-adds.c Sat Oct 8 16:43:37 2005 @@ -39,4 +39,36 @@ return gtk_tree_iter_copy(&example); } +int gtk_adds_widget_mapped_p (GtkWidget *wid) +{ + return ((GTK_WIDGET_FLAGS (wid) & GTK_MAPPED) != 0) ? 1 : 0; +} + +int gtk_adds_widget_visible_p (GtkWidget *wid) +{ + return ((GTK_WIDGET_FLAGS (wid) & GTK_VISIBLE) != 0) ? 1 : 0; +} + +GdkWindow * +gtk_adds_widget_window (GtkWidget *wid) +{ + return wid->window; +} + +GdkColor * +gtk_adds_color_new () +{ + return ((GdkColor *)malloc(sizeof(GdkColor))); +} + +void +gtk_adds_color_set_rgb (GdkColor* color, guint r, guint g, guint b) +{ + color->red = r; + color->green = g; + color->blue = b; +} + + +

1 0

[cells-gtk-cvs] CVS update: root/gtk-ffi/Makefile
by pdenno＠common-lisp.net 08 Oct '05

08 Oct '05

Update of /project/cells-gtk/cvsroot/root/gtk-ffi In directory common-lisp.net:/tmp/cvs-serv15105/root/gtk-ffi Modified Files: Makefile Log Message: Better comments. Date: Sat Oct 8 16:34:15 2005 Author: pdenno Index: root/gtk-ffi/Makefile diff -u root/gtk-ffi/Makefile:1.1 root/gtk-ffi/Makefile:1.2 --- root/gtk-ffi/Makefile:1.1 Sat Feb 26 23:17:52 2005 +++ root/gtk-ffi/Makefile Sat Oct 8 16:34:15 2005 @@ -1,21 +1,21 @@ # # Purpose: build libcellsgtk.so # -# You don't need libCellsGtk.so to run the demo, but you will to add an entry -# text widget to a dialog, or add menu items using populate-popup (see GTK textview). +# You don't need libCellsGtk.so to run the demo, but you will to +# - add an entry text widget to a dialog +# - add menu items using populate-popup (see GTK textview). +# - Use a TreeModel (hierarchical arrangment of items) in a ComboBox. +# # As of this writing, those are the only situations where it is needed. See FAQ.txt # for more of the motivation. # # In order to compile the library you will need to have on hand the C header files # corresponding the libgtk.so you are using. # See http://developer.gnome.org/doc/API/2.4/gtk/gtk-building.html -# On linux, it is a matter of installing 4 or 5 .rpms and typing "make", -# or at least that is how it worked for me. +# On linux, it is a matter of installing 4 or 5 .rpms and typing "make" +# Or at least that is how it worked for me. # # Once built, place the library in the directory containing libgtk. -# #-mswindows ../load.lisp will push :libcellsgtk onto *features* -# #+mswindows you will have to push :libcellsgtk onto *features* yourself. -# all: gcc -c gtk-adds.c `pkg-config --cflags --libs gtk+-2.0`

1 0

[cells-gtk-cvs] CVS update: root/cells-gtk/widgets.lisp
by pdenno＠common-lisp.net 08 Oct '05

08 Oct '05

Update of /project/cells-gtk/cvsroot/root/cells-gtk In directory common-lisp.net:/tmp/cvs-serv15074/root/cells-gtk Modified Files: widgets.lisp Log Message: Export method widget-id. Same as cgtk::id, (but without the potential package problems of exporting that). Date: Sat Oct 8 16:33:19 2005 Author: pdenno Index: root/cells-gtk/widgets.lisp diff -u root/cells-gtk/widgets.lisp:1.13 root/cells-gtk/widgets.lisp:1.14 --- root/cells-gtk/widgets.lisp:1.13 Sun May 29 23:15:51 2005 +++ root/cells-gtk/widgets.lisp Sat Oct 8 16:33:19 2005 @@ -298,12 +298,10 @@ (not-to-be old-value)) (when new-value (gtk-widget-set-popup (id self) (id (to-be new-value))))) - + (def-c-output visible ((self widget)) - (when *gtk-debug* - (trc nil "VISIBLE" (md-name self) new-value) (force-output)) - (if new-value - (gtk-widget-show (id self)) + (if new-value + (gtk-widget-show (id self)) (gtk-widget-hide (id self)))) (def-c-output tooltip ((self widget)) @@ -353,7 +351,7 @@ (def-c-output title ((self window)) (when new-value - (gtk-window-set-title (id self) new-value))) + (gtk-window-set-title (id self) new-value))) (def-c-output icon ((self window)) (when new-value @@ -394,5 +392,9 @@ (when new-value (gtk-container-add (id self) (id (first new-value)))) #+clisp (call-next-method)) + +(defun widget-id (widget) + (id widget)) + (eval-when (compile load eval) - (export '(callback callback-if timeout-add focus))) + (export '(callback callback-if timeout-add focus widget-id)))

1 0

[cells-gtk-cvs] CVS update: root/cells-gtk/textview.lisp
by pdenno＠common-lisp.net 08 Oct '05

08 Oct '05

Update of /project/cells-gtk/cvsroot/root/cells-gtk In directory common-lisp.net:/tmp/cvs-serv15045/root/cells-gtk Modified Files: textview.lisp Log Message: Added textview-scroll-to-position (but see discussion in FAQ about connecting a stream to textview for a better approach). Date: Sat Oct 8 16:31:24 2005 Author: pdenno Index: root/cells-gtk/textview.lisp diff -u root/cells-gtk/textview.lisp:1.4 root/cells-gtk/textview.lisp:1.5 --- root/cells-gtk/textview.lisp:1.4 Sun Mar 6 17:58:51 2005 +++ root/cells-gtk/textview.lisp Sat Oct 8 16:31:24 2005 @@ -130,6 +130,16 @@ (gtk-text-buffer-get-iter-at-offset buf e-iter end) (gtk-text-buffer-delete buf s-iter e-iter)))) +;;; This isn't working perfectly. Might be better to use gtk-text-view-scroll-mark-onscreen +;;; I do just that in one of my applications, but since it requires a mark, I didn't write +;;; an exported function for it. +(defun text-view-scroll-to-position (textview pos) + (let* ((view (id textview)) + (buf (gtk-text-view-get-buffer view))) + (with-text-iters (s-iter) + (gtk-text-buffer-get-iter-at-offset buf s-iter pos) + (gtk-text-view-scroll-to-iter view s-iter 0.0 nil 0.0 0.0)))) + ;;; The next two can be used to check and clear the the modified flag. ;;; The event is registered when you use :on-modified-changed on a text-buffer. ;;; The def-c-output text ((text-buffer)) clears the flag so as to distinguish @@ -143,7 +153,10 @@ (eval-when (:compile-toplevel :load-toplevel :execute) (export '(def-populate-adds populate-adds with-text-iters text-buffer-get-text - text-buffer-delete-text text-buffer-insert-text text-buffer-modified-p))) + text-buffer-delete-text text-buffer-insert-text text-buffer-modified-p + text-view-scroll-to-position gtk-text-buffer-get-iter-at-offset + gtk-text-buffer-create-mark gtk-text-view-set-wrap-mode gtk-text-view-set-editable + gtk-text-buffer-move-mark gtk-text-view-scroll-mark-onscreen)))

1 0

[cells-gtk-cvs] CVS update: root/cells-gtk/cells-gtk.asd
by pdenno＠common-lisp.net 08 Oct '05

08 Oct '05

Update of /project/cells-gtk/cvsroot/root/cells-gtk In directory common-lisp.net:/tmp/cvs-serv14066/root/cells-gtk Modified Files: cells-gtk.asd Log Message: Added load of drawing.lisp Date: Sat Oct 8 16:29:28 2005 Author: pdenno Index: root/cells-gtk/cells-gtk.asd diff -u root/cells-gtk/cells-gtk.asd:1.4 root/cells-gtk/cells-gtk.asd:1.5 --- root/cells-gtk/cells-gtk.asd:1.4 Sun May 29 23:03:43 2005 +++ root/cells-gtk/cells-gtk.asd Sat Oct 8 16:29:28 2005 @@ -11,6 +11,7 @@ (:file "widgets" :depends-on ("conditions")) (:file "layout" :depends-on ("widgets")) (:file "display" :depends-on ("widgets")) + (:file "drawing" :depends-on ("widgets")) (:file "buttons" :depends-on ("widgets")) (:file "entry" :depends-on ("widgets")) (:file "tree-view" :depends-on ("widgets"))

1 0

[cells-gtk-cvs] CVS update: root/cells-gtk/menus.lisp
by pdenno＠common-lisp.net 08 Oct '05

08 Oct '05

Update of /project/cells-gtk/cvsroot/root/cells-gtk In directory common-lisp.net:/tmp/cvs-serv14035/root/cells-gtk Modified Files: menus.lisp Log Message: New method cgtk-set-active-item-by-path (on combo-box) Date: Sat Oct 8 16:28:49 2005 Author: pdenno Index: root/cells-gtk/menus.lisp diff -u root/cells-gtk/menus.lisp:1.10 root/cells-gtk/menus.lisp:1.11 --- root/cells-gtk/menus.lisp:1.10 Sun May 29 23:09:40 2005 +++ root/cells-gtk/menus.lisp Sat Oct 8 16:28:49 2005 @@ -18,6 +18,8 @@ (in-package :cgtk) +(export '(cgtk-set-active-item-by-path)) + (defmacro with-tree-iters (vars &body body) `(let (,@(loop for var in vars collect `(,var (gtk-adds-tree-iter-new)))) (unwind-protect @@ -40,7 +42,7 @@ :new-tail '-text :on-changed (callback (widget event data) - (trc nil "combo-box onchanged cb" widget event data (id self)) + ;(trc nil "combo-box onchanged cb" widget event data (id self)) (if (items self) ;; flat model (:items specified) (let ((pos (gtk-combo-box-get-active (id self)))) @@ -74,12 +76,19 @@ for index from 0 do (gtk-tree-store-set-kids (id (tree-model self)) root c-null index '(:string :string) pfunc (children-fn self))) - ;; Spec says iter must correspond to a path of depth one. Hence no point in set-active-iter. - ;; init should just be the index of the depth one item you want displayed. - (bwhen (item-index (init self)) - (gtk-combo-box-set-active (id self) item-index) - (let ((item (item-from-path (children-fn self) (roots self) (list item-index)))) - (setf (md-value self) item)))))) + ;; Spec says iter must correspond to a path of depth one. But then there would be no point + ;; in set-active-iter. Well, the spec seems to be wrong (or poorly worded). + (bwhen (path (init self)) + (cgtk-set-active-item-by-path self path))))) + +(defmethod cgtk-set-active-item-by-path ((self combo-box) path) + "Sets the value of the tree-model type combo-box to the item at the path. Path is a list of integers." + (bwhen (tree (tree-model self)) + (with-tree-iters (it) + (when (gtk-tree-model-get-iter-from-string (id tree) it (format nil "~{~A~^:~}" path)) + (gtk-combo-box-set-active-iter (id self) it) + ;(break "in cgtk setting path = ~A" path) + (setf (md-value self) (item-from-path (children-fn self) (roots self) path)))))) (def-c-output items ((self combo-box)) (when old-value @@ -88,11 +97,11 @@ (when new-value (dolist (item (items self)) (gtk-combo-box-append-text (id self) (funcall (print-fn self) item))) - (when (init self) - (let ((index (position (init self) (items self)))) - (when index - (gtk-combo-box-set-active (id self) index) - (setf (md-value self) (init self))))))) + (bif (index (position (init self) (items self))) + (progn (gtk-combo-box-set-active (id self) index) + (setf (md-value self) (init self))) + (progn (gtk-combo-box-set-active (id self) 0) + (setf (md-value self) (car (items self))))))) ;;; ============= Toolbar/Toolbutton ============================ (def-object tooltips () @@ -295,3 +304,4 @@ (def-widget tearoff-menu-item (menu-item) () () ()) +(export '(gtk-combo-box-set-active)) \ No newline at end of file

1 0

[cells-gtk-cvs] CVS update: root/cells-gtk/drawing.lisp
by pdenno＠common-lisp.net 08 Oct '05

08 Oct '05

Update of /project/cells-gtk/cvsroot/root/cells-gtk In directory common-lisp.net:/tmp/cvs-serv14010/root/cells-gtk Added Files: drawing.lisp Log Message: New file implementing DrawingArea -- needs work, but getting there. Date: Sat Oct 8 16:26:42 2005 Author: pdenno

1 0

[cells-gtk-cvs] CVS update: public_html/faq.html
by pdenno＠common-lisp.net 03 Oct '05

03 Oct '05

Update of /project/cells-gtk/cvsroot/public_html In directory common-lisp.net:/tmp/cvs-serv869 Modified Files: faq.html Log Message: minor Date: Mon Oct 3 16:43:47 2005 Author: pdenno Index: public_html/faq.html diff -u public_html/faq.html:1.9 public_html/faq.html:1.10 --- public_html/faq.html:1.9 Sun Oct 2 21:04:39 2005 +++ public_html/faq.html Mon Oct 3 16:43:46 2005 @@ -210,7 +210,7 @@ Q: What is the difference between using c-input (AKA c-in) and c-formula (AKA c?) in a slot's :initform ? A:The two define different kinds of cells: -A c-input cell is a cell whose value may be set through explicit declarative code, such as by using setf on the slot. +A c-input cell is a cell whose value may be set through explicit procedural code, using setf on the slot. A c-formula cell is a cell whose value is obtained through evaluation of a formula.

1 0

[cells-gtk-cvs] CVS update: public_html/faq.html
by pdenno＠common-lisp.net 02 Oct '05

02 Oct '05

Update of /project/cells-gtk/cvsroot/public_html In directory common-lisp.net:/tmp/cvs-serv15592 Modified Files: faq.html Log Message: reflects some suggestions from kt Date: Sun Oct 2 21:04:39 2005 Author: pdenno Index: public_html/faq.html diff -u public_html/faq.html:1.8 public_html/faq.html:1.9 --- public_html/faq.html:1.8 Sat Oct 1 21:03:15 2005 +++ public_html/faq.html Sun Oct 2 21:04:39 2005 @@ -36,7 +36,8 @@ <li><a href="#q6">What GTK Widgets are implemented in cells-gtk?</a></li> <li><a href="#q7">Do I have to use cells?</a></li> <li><a href="#q8">What is libcellsgtk.so about?</a></li> - <li><a href="#q8.5">What is the difference between using c-in and c? in a slot's :initform?</a></li> + <li><a href="#q8.5">What is the difference between using c-input (AKA c-in) and c-formula (AKA c?) in a + slot's :initform?</a></li> <li><a href="#q9">Why do I need :owner here? It looks like c? would bind self to the mk-whatever enclosing the c?</a></li> <li><a href="#q10">How do I do xyz?</a></li> @@ -61,46 +62,55 @@ A: From the Cells website: "Cells is a mature, stable extension to CLOS that allows you to create classes, the instances of which have slots whose values are determined by a formula." - Here is an explanation from the viewpoint of a Cells-GTK programmer: + +From <a href='http://bc.tech.coop/blog/030911.html'>Bill Clementson's Blog</a>: + "...Cells allows you to define classes whose slots can be dynamically + (and automatically) updated and for which standard 'observers' can be defined that react to changes + in those slots." + + Here is an explanation from the viewpoint of a Cells-GTK programmer: Cells provides Cells-GTK with two essential features: (1) a part-subpart relationship, as is typically found in GUIs -- it allows the user to express that, e.g., this window contains these buttons and subwindows etc.; (2) the expression of a program's state machine, as viewed from the context of the user's interaction through the GUI. This last point is especially noteworthy, and needs more explanation. If you are at all familiar with developing moderately complex software - that is operated through a GUI, then you have probably learned this: Keeping what is presented through + that is operated through a GUI, then you have probably learned this lesson: Keeping what is presented through the GUI in-sync with what the user is allowed to do, and in-sync with the computational state of the program is often tedious, complicated work. Specifically, there are the issues of what menu items ought to be made sensitive when, what items should be presented in list, what text should appear in entries, etc. Cells-GTK helps with these tasks by providing an abstraction over the details; each - of the tasks just listed can be controlled by (a) rules that specify the value of attributes of graphic - features in the part-subpart declaration (that declaration is called 'defpart' in cells-gtk); - and, (b) rules that specify the value of CLOS slots. [Footnote, In the details of the implementation, + of the tasks just listed can be controlled by (a) formula that specify the value of attributes of graphic + features in the part-subpart declaration (that declaration is called 'defpart' in cells-gtk); + and, (b) formula that specify the value of CLOS slots. [Footnote, In the details of the implementation, (a) is just a usage of (b). But it helps to think of the ability to set a GUI feature with a - rule as something different than setting the value of slot with a rule.]. An example of (a) - is setting the :sensitive feature of a GTK menu item. For this, I might use the rule (c? (user-file *my-gui*)). + formula as something different than setting the value of slot with a formula.]. (c) 'observers' (to + use Bill Clementson's term) that watch over GUI features and react to changes. + + An example of (a) + is setting the :sensitive feature of a GTK menu item. For this, I might use the formula (c? (user-file *my-gui*)). Here user-file is the accessor of some object *my-gui*. :sensitive is a boolean, so whenever there is a non-nil value in the slot user-file, the menu item is sensitive. That doesn't look a whole lot different than giving :sensitive whatever value (user-file *my-gui*) evaluates to. The difference is that in Cells-GTK, the Cells codes watches over 'instrumented' slots such as user-file and automatically updates those attributes of a Cell-GTK object (such as a menu item's :sensitive feature) - that are governed by a Cells rule. Thus, I don't have to explicitly update the value of + that are governed by a Cells formula. Thus, I don't have to explicitly update the value of :sensitive -- it happens automatically. So what is this talk about 'expression of a program's state machine?' Well, the idea is that - in a GUI operated by Cells-GTK, transition into a state is governed by cells-rules on + in a GUI operated by Cells-GTK, transition into a state is governed by cells-formulae on GUI features and cells-instrumented slots. E.g. when the user loads a file, (c? (user-file *my-gui*)) becomes true and the program enters the state where some menu item that wasn't sensitive now is - -- the cells rules are rules on the arcs out of states. Is that stretching it too much? + -- the cells formulae are formulae on the arcs out of states. Is that stretching it too much? I don't know, it makes sense to me. See also: <ul> + <li><a href='http://bc.tech.coop/blog/030911.html'> + Bill Clementson's Blog</a></li> <li><a href="http://common-lisp.net/project/cells/"> http://common-lisp.net/project/cells/</a></li> <li><a href="http://www.tilton-technology.com/cells_top.html"> http://www.tilton-technology.com/cells_top.html</a></li> - <li><a href="http://home.comcast.net/~bc19191/2003_09_07_bill-clementson_archive.html"> - http://home.comcast.net/~bc19191/2003_09_07_bill-clementson_archive.html</a></li> </ul> @@ -197,10 +207,16 @@ -Q: What is the difference between using c-in and c? in a slot's :initform ? -A: The usual semantics of :initform do not apply when :initform is given a c? rule. -Instead of just setting the value at initialization, when c? is used, the value of the slot is -checked and updated using the rule throughout program execution. +Q: What is the difference between using c-input (AKA c-in) and c-formula (AKA c?) in a slot's +:initform ? +A:The two define different kinds of cells: +A c-input cell is a cell whose value may be set through explicit declarative code, such as by using setf on the slot. + +A c-formula cell is a cell whose value is obtained through evaluation of a formula. + +Note that the usual semantics of :initform do not apply when :initform is given by c-formula. +Instead of just setting the value at initialization, the c-formula (an arbitrary lisp form) +specifies the dynamic relationship between the slot's value and other aspects of the program state. Q: Why do I need :owner here? It looks like c? would bind self to the mk-whatever

1 0

[cells-gtk-cvs] CVS update: public_html/cgtk-primer.html public_html/faq.html
by pdenno＠common-lisp.net 01 Oct '05

01 Oct '05

Update of /project/cells-gtk/cvsroot/public_html In directory common-lisp.net:/tmp/cvs-serv12344 Modified Files: cgtk-primer.html faq.html Log Message: a few more FAQ answers. Date: Sat Oct 1 21:03:16 2005 Author: pdenno Index: public_html/cgtk-primer.html diff -u public_html/cgtk-primer.html:1.3 public_html/cgtk-primer.html:1.4 --- public_html/cgtk-primer.html:1.3 Mon Mar 7 00:37:35 2005 +++ public_html/cgtk-primer.html Sat Oct 1 21:03:15 2005 @@ -147,7 +147,7 @@ propagation to formula-valued cell dependencies has to happen before any output SETF (and why Cells has a mechanism to defer SETFs of inputs). -<h1>Family: Referencing slots throughout the defmodel hierarchy.</h1> +<h1>Family: Referencing cells throughout the defmodel hierarchy.</h1> The defmodel macro defines a part-subpart relationship among components of the interface. The relationship is made by the @@ -160,7 +160,7 @@ <address><a href="mailto:peter.denno@nist.gov">Peter Denno</a></address>   -Last modified: Sun Mar 6 18:36:16 EST 2005 +Last modified: Sun Mar 6 18:43:09 EST 2005  </div> </body> Index: public_html/faq.html diff -u public_html/faq.html:1.7 public_html/faq.html:1.8 --- public_html/faq.html:1.7 Mon Mar 7 00:38:22 2005 +++ public_html/faq.html Sat Oct 1 21:03:15 2005 @@ -36,18 +36,22 @@ <li><a href="#q6">What GTK Widgets are implemented in cells-gtk?</a></li> <li><a href="#q7">Do I have to use cells?</a></li> <li><a href="#q8">What is libcellsgtk.so about?</a></li> + <li><a href="#q8.5">What is the difference between using c-in and c? in a slot's :initform?</a></li> <li><a href="#q9">Why do I need :owner here? It looks like c? would bind self to the mk-whatever enclosing the c?</a></li> <li><a href="#q10">How do I do xyz?</a></li> - <li><a href="#q11">Q: What does this error mean? : "cellular slot FOO of #<BAR 21B555A4> cannot be setf - unless initialized as inputp.</a></li> - <li><a href="#q12">Q: Changing a cell value causes dependencies to fire, but what is considered a change?</li> + <li><a href="#q11">What does this error mean? : "cellular slot FOO of #<BAR 21B555A4> cannot be setf + unless initialized as inputp."</a></li> + <li><a href="#q12">Changing a cell value causes dependencies to fire, but what is considered a change?</li> + <li><a href="#q13">Can I keep a window around for redisplay after using the window border + 'delete' button to delete it?</a></li> + </ul> Q: What is Cells-GTK? -A: Cells-GTK is a GTK binding to lisp written by Vasilis Margioulas. It uses the +A: Cells-GTK is a lisp binding of GTK written by Vasilis Margioulas. It uses the Cells system, a sort of constraint propagation system written by kenny tilton. (see "What is Cells?"). As of this writing Cells-GTK runs under Allegro, Lispworks and CMUCL. A separate distribution (not quite up to date with the former) runs @@ -56,7 +60,39 @@ Q: What is Cells? A: From the Cells website: "Cells is a mature, stable extension to CLOS that allows you to create classes, the instances of which have slots whose values are determined by - a formula." + a formula." + Here is an explanation from the viewpoint of a Cells-GTK programmer: + Cells provides Cells-GTK with two essential features: (1) a part-subpart relationship, + as is typically found in GUIs -- it allows the user to express that, e.g., this window contains these + buttons and subwindows etc.; (2) the expression of a program's state machine, as viewed from the + context of the user's interaction through the GUI. This last point is especially noteworthy, and + needs more explanation. If you are at all familiar with developing moderately complex software + that is operated through a GUI, then you have probably learned this: Keeping what is presented through + the GUI in-sync with what the user is allowed to do, and in-sync with the computational state of + the program is often tedious, complicated work. Specifically, there are the issues of what menu items + ought to be made sensitive when, what items should be presented in list, what text should appear in + entries, etc. Cells-GTK helps with these tasks by providing an abstraction over the details; each + of the tasks just listed can be controlled by (a) rules that specify the value of attributes of graphic + features in the part-subpart declaration (that declaration is called 'defpart' in cells-gtk); + and, (b) rules that specify the value of CLOS slots. [Footnote, In the details of the implementation, + (a) is just a usage of (b). But it helps to think of the ability to set a GUI feature with a + rule as something different than setting the value of slot with a rule.]. An example of (a) + is setting the :sensitive feature of a GTK menu item. For this, I might use the rule (c? (user-file *my-gui*)). + Here user-file is the accessor of some object *my-gui*. :sensitive is a boolean, so whenever there + is a non-nil value in the slot user-file, the menu item is sensitive. That doesn't look a whole lot + different than giving :sensitive whatever value (user-file *my-gui*) evaluates to. + The difference is that in Cells-GTK, the Cells codes watches over 'instrumented' slots such as user-file + and automatically updates those attributes of a Cell-GTK object (such as a menu item's :sensitive feature) + that are governed by a Cells rule. Thus, I don't have to explicitly update the value of + :sensitive -- it happens automatically. + + So what is this talk about 'expression of a program's state machine?' Well, the idea is that + in a GUI operated by Cells-GTK, transition into a state is governed by cells-rules on + GUI features and cells-instrumented slots. E.g. when the user loads a file, (c? (user-file *my-gui*)) + becomes true and the program enters the state where some menu item that wasn't sensitive now is + -- the cells rules are rules on the arcs out of states. Is that stretching it too much? + I don't know, it makes sense to me. + See also: <ul> <li><a href="http://common-lisp.net/project/cells/"> @@ -68,6 +104,7 @@ </ul> + Q: Why is the Clisp distribution separate? A: Because as of this writing, UFFI, which Cells-GTK uses, doesn't support CLISP. @@ -82,7 +119,22 @@ Q: What GTK Widgets are implemented in cells-gtk? A: [hmm, Better to ask what isn't. Most of the useful widgets are implemented, but - among those, many non-essential methods are not.] + among those, many non-essential methods are not.] A quick look at the +<a href="http://developer.gnome.org/doc/API/2.0/gtk/ch02.html">widget gallery</a>. These +are not implemented: +<ul> + <li>GtkColorButton</li> + <li>GtkFileChooserButton </li> + <li>GtkFontButton </li> + <li>GtkIconView</li> + <li>GtkStatusBar</li> + <li>GtkFontSelectionDialog</li> + <li>GtkColorSelectionDialog</li> +</ul> +There are quite a few other widgets not listed in the Gallery that aren't implmented. +But BTW, it isn't difficult to implement most of these. If you need one, implemented +it and drop us a note! + Q: Do I have to use cells? A: Probably not. But the demo uses them, so it might still be (despite the lack of @@ -143,6 +195,14 @@ the libgtk.so you are using. + + +Q: What is the difference between using c-in and c? in a slot's :initform ? +A: The usual semantics of :initform do not apply when :initform is given a c? rule. +Instead of just setting the value at initialization, when c? is used, the value of the slot is +checked and updated using the rule throughout program execution. + + Q: Why do I need :owner here? It looks like c? would bind self to the mk-whatever enclosing the c? <tt> @@ -179,7 +239,7 @@ </pre> </tt> -A: If you macroexpand callback, you will see that ith binds self again, this time to the +A: If you macroexpand callback, you will see that it binds self again, this time to the menu-item. <tt>(owner self)</tt> gets you into the :kids hierarchy. Q: How do I do xyz? @@ -200,6 +260,25 @@ dependencies to fire again (in order to save substantial useless recalculations). So how is "equivalence" defined? EQL is used unless overridden by providing a function of two arguments to :unchanged-if in the slot definition of the defmodel. + + + +Q: Can I keep a window around for redisplay after using the window border + 'delete' button to delete it? + A:Yes. Do something like this: + +<tt> +<pre> +(defmodel pseudo-dialog (window) + () + (:default-initargs + :on-delete-event (callback (w e d) (gtk-widget-hide-on-delete w)))) +</pre> +</tt> + +... and, of course, store the widget somewhere so you can later display it with + (gtk-widget-show-all (widget-id my-pseudo-dialog)). + <hr/> <address><a href="mailto:peter.denno@nist.gov">Peter Denno</a></address>

1 0