cells-devel April 2008

cells-devel@common-lisp.net

9 participants
36 discussions

Start a nNew thread

[cells-devel] penetrate deeper
by Noreen 25 Apr '08

25 Apr '08

GAIN YOUR PENIS 2 INCH - SIMPLE AS NEVER. NATURAL HERBAL PRODUCT 100% SATISFACTION GUARANTEE! http://babbuyae.com

1 0

Re: [cells-devel] not-to-be and owning slots
by Peter Hildebrandt 23 Apr '08

23 Apr '08

On Tue, Apr 22, 2008 at 2:33 AM, Ken Tilton <kennytilton(a)optonline.net> wrote: > Later on I saw you reporting something weird about .kids not getting > reliably handled. I' d like to run down the "weird" rather than just throw > in parallel code to make .kids work. After I commit lemme know when the > weirdness returns. Sounds good. I wasn't sure as to whether I understood what I was doing. I just saw that not-to-be did not propagate to kids *at all* if I did it the way I suggested. Hold on, one idea: Maybe the problem is with (get (type-of fm) :ownings), i.e. this only picks up the owning defined on the actual class of fm, not the inherited ones? To be honest, I am just doing wild guesswork here, so I better shut up :-) Hope you guys had a good time in Amsterdam. Hopefully next year I will actually make it :-) Cheers, Peter

2 7

[cells-devel] not-to-be fix, better diagnostics
by Ken Tilton 23 Apr '08

23 Apr '08

Thx to Peter for noticing not-to-be was not propagating to "owned" stuff --that seems to be working better now, but we'll keep a watch on that. Along the way I added a helpful debugging tool. If one specifies :cells-debug t ...to cells-reset the integrity dataflow propagation records what it does and then in the event of a backtrace prints it all out before doing a describe on the error condition. One can also specify a function as the :cells-debug value. Here is the one I used to debug a problem today: (a1-reset :cells-debug (lambda (c is) (loop for (id . info) in is unless (find id '(:ephemeral-reset :awaken)) do (format t "~&a1> ~(~a > ~a~) " id info) finally (describe c) (break "integ backtrace: see listener for deets")))) The info is just whatever gets supplied as the "defer-info" when something gets queued up for integrity handling, ie, the second parameter to the with-integrity macro. kt

1 0

[cells-devel] Optimized away/dying rules
by Peter Hildebrandt 22 Apr '08

22 Apr '08

While working on the hash-table lookup for md-names (as an alternative to fm-other) I came across an interesting phenomenon: Some rules die, others don't. Following the XP idea for RFEs, I'll try to present a test case: (defpackage :c-test (:use :cl :cells :utils-kt)) (in-package :c-test) (defparameter *hash* (make-hash-table)) (defun val (name) (bwhen (obj (gethash name *hash*)) (value obj))) (defparameter *m1* (make-instance 'model :value (c? (bif (v (val :foo)) (1+ v) 'nothing)))) (assert (eql (value *m1*) 'nothing)) (setf (gethash :foo *hash*) (make-instance 'model :value (c-in nil))) (defparameter *m2* (make-instance 'model :value (c? (bif (v (val :foo)) (1+ v) 'nothing)))) (assert (eql (value *m1*) 'nothing)) (assert (eql (value *m2*) 'nothing)) (setf (value (gethash :foo *hash*)) 42) (assert (eql (value *m1*) 43)) ;;; #### FAILS #### (assert (eql (value *m2*) 43)) ;;; ok (setf (value (gethash :foo *hash*)) 17) (assert (eql (value *m1*) 18)) ;;; #### FAILS #### (assert (eql (value *m2*) 18)) ;;; ok ;;; or with a list (defparameter *list* nil) (defun valb (name) (bwhen (obj (assocd name *list*)) (value obj))) (defparameter *m1b* (make-instance 'model :value (c? (bif (v (valb :foo)) (1+ v) 'nothing)))) (assert (eql (value *m1b*) 'nothing)) (push (cons :foo (make-instance 'model :value (c-in nil))) *list*) (defparameter *m2b* (make-instance 'model :value (c? (bif (v (valb :foo)) (1+ v) 'nothing)))) (assert (eql (value *m1b*) 'nothing)) (assert (eql (value *m2b*) 'nothing)) (setf (value (assocd :foo *list*)) 17) (assert (eql (value *m1b*) 18)) ;;; #### FAILS #### (assert (eql (value *m2b*) 18)) ;;; ok (setf (value (assocd :foo *list*)) 42) (assert (eql (value *m1b*) 43)) ;;; #### FAILS #### (assert (eql (value *m2b*) 43)) ;;; ok -------- An interesting indicator might be that the first call to (value *m1*) returns two values, 'nothing and nil -- does that mean that cells somehow realizes there that this cell can be optimized out? And -- more importantly -- how can I tell cells not to optimize away the ruled cell in *m1*/*m1b*? Thanks, Peter

3 8

[cells-devel] not-to-be and owning slots
by Peter Hildebrandt 21 Apr '08

21 Apr '08

I came across something, which seem odd to me: - If I remove an instance from a kids slot, not-to-be is called on that instance - If I remove an instance form any :owning t slot, not-to-be is called on that instance - If not-to-be is called on an instance, it is also called on all its kids BUT If not-to-be is called on an instance, it is NOT called on all instances its :owning t slots. Is this desired behavior, or dfid it get overlooked when owning was introduced? What is the recommended way to deal with it? - write a not-to-be method for my specific class which setfs the owned slots to nil to trigger not-to-be? - write a not-to-be method for my specific class which mapcs not-to-be over its owned slots? or - fix it in cells and change not-to-be there so it does not only recurse down kids, but all owned slots? Thanks for any advice, Peter

1 2

[cells-devel] [openair] web-app still :NASCENT after make-instance
by Frank Goenninger 19 Apr '08

19 Apr '08

Ok, so I am still trying to find out why the handler slot of the web app is always NIL. That's what I get after creating the instance with make-instance: 0> 72657 *** BINGO request !!! #<tbnl::request @ #x10cadc6a> "/ht- monitor" "/ht-monitor" openair::ht-monitor 0> 0 *** Entering page handling ... 0> 0 creating new web-app... 0> 0 ROOT = web-app6 WEB-APP6 is an instance of #<STANDARD-CLASS OPENAIR::WEB-APP>: The following slots have :INSTANCE allocation: .MD-STATE :NASCENT .AWAKEN-ON-INIT-P NIL .CELLS ((OPENAIR::HANDLER . ) (OPENAIR::RESOURCE . ) (OPENAIR::UPDATES . ) (OPENAIR::MESSAGE . ) (OPENAIR::REQUEST . ) (CELLS:.KIDS . )) .CELLS-FLUSHED NIL ADOPT-CT 0 .MD-NAME WEB-APP6 .FM-PARENT NIL .VALUE NIL ZDBG NIL .KID-SLOTS NIL .KIDS NIL PREFIX "/ht-monitor" REQUEST NIL MESSAGE NIL UPDATES NIL RESOURCE NIL HANDLER NIL Now, as we can see, the .MD-STATE is :NASCENT - so Cell's machinery hasn't done its job conpletely yet... Kenny, how can we force Cells to finish its business ?! Or is there any other way to do this? Thanks for any help! (see below for the full function) Best, Frank -X- CODE -X- (defun ht-monitor-page (prefix resource-class) (lambda (request) (trc "*** BINGO request !!!" request (script-name request) prefix resource-class) ;; New here: only go into the actual function if we are really meant ... (let ((mismatch (mismatch (script-name request) prefix :test #'char=))) (and (or (null mismatch) (>= mismatch (length prefix))) (progn (trc "*** Entering page handling ...") (start-session) (let ((root (or (bwhen (r (session-value 'root)) (trc "clearing updates on re-used root!!!!!!!" r) (with-integrity () (setf (updates r) nil)) r) (progn (trc "creating new web-app...") (mk-web-app (:prefix prefix :request (c-in nil)) (make-instance resource-class :fm-parent *parent*)))))) (trc "ROOT = " root) (describe root) (setf (session-value 'root) root) (setf (request root) request) (assert (handler root)) (trc "Handler is: " (describe (handler root))) (handler root)))))))

2 1

[cells-devel] Added cells-store to cells
by Peter Hildebrandt 17 Apr '08

17 Apr '08

As promised yesterday I added a cells-store facility to cells. The code can be found at the bottom of md-utilities in CVS. Basically, this is a cells-aware hash table with some syntactic sugar. Here's part of the test function included in md-utilities: (defun test-cells-store () (trc "testing cells-store -- making objects") (let* ((store (make-instance 'cells-store)) (foo (make-instance 'test-store-item :value (c?-with-stored (v :foo store 'nothing) (bwhen (val (value v)) val)))) (foo+1 (make-instance 'test-store-item :value (c?-with-stored (v :foo store 'nothing) (bwhen (val (value v)) (1+ val)))))) (store-add :foo store (make-instance 'family :value (c-in nil))) (setf (value (store-lookup :foo store)) 1) (store-remove :foo store)) So you create a ruled cell with c?-with-stored. This can happen before or after key is added to the cells-store. When the rule is the executed, when an object is added or removed from key in the hash table *or* when any of the cells on the object change. The rule is not executed, if other stuff in the hash table changes. The (c?-with-stored (var key store &optional default) &body body) macro works like bwhen -- that is, if key is present, body is executed with var bound to the object identified by key -- and if not, default is returned. That means, body can assume that var is bound to a valid object (like in the example, it is safe to call value on it, if you know that you only store family instances in the store) Calling store-remove will reset all dependent cells to their default. The change is propagated as soon as store-add, setf, or store-remove are called -- meaning that observers will do the expected thing. Maybe someone will find it useful. Peter

3 3

[cells-devel] [openair] Scratching my head ...
by Frank Goenninger 15 Apr '08

15 Apr '08

Hmmm. So there's this function I "borrowed" from Kenny's code: (defun ht-monitor-page (path resource-class) (lambda (request) (trc "bingo request!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!" request path resource-class) (start-session) (let ((root (or (bwhen (r (session-value 'root)) (trc "clearing updates on re-used root!!!!!!!" r) (setf (updates r) nil) r) (progn (trc "creating new web-app...") (mk-web-app (:prefix path :request (c-in request)) ;; was (c-in request) but we set that below so ??? (make-instance resource-class :fm-parent *parent*)))))) (trc "ROOT = " root) (setf (session-value 'root) root) (setf (request root) request) #+test-ht-monitor (break) ;; <<<<<<<-- See here ;; (assert (handler root)) ;; <<<<<<<-- AND HERE ! ALWAYS FAILS ! (trc "Handler is: " (describe (handler root))) (trc "******* Calling handler ") (handler root)))) My model is quite simple: (defmd ht-monitor (page) name ip-address term :title ":: HUNCHENTOOT MONITOR ::" :style "/css/ht-monitor.css" :name (c? (server-name *server*)) :ip-address (c? (server-address *server*)) :term (c-in "") :kids (c? (the-kids (mk-div () (mk-text (c? (conc$ "Name: " (name (u^ ht-monitor)))))) (mk-div () (mk-text (c? (conc$ "IP Address: " (ip-address (u^ ht- monitor)))))) (mk-div () (mk-form (:action :get) (mk-text "Input: ") (mk-input (:name "i" :id "i" :-type "text" :value (c?n (term (u^ ht-monitor))))) (mk-text (c? (conc$ "Reversed: " (reverse (term (u^ ht-monitor))))))))))) Handler is always NIL. The assertion always fails. I could not figure out why... Any ideas ??? Thx! Best, Frank

2 1

[cells-devel] [openair] recv function ?!
by Frank Goenninger 15 Apr '08

15 Apr '08

Andy, I am currently trying to figure out why I don't get any update on my browser of, if any, just once. When looking at the recv function in openair.js I see: function recv (data) { var response = eval("[" + data + "]"); for(var i=0; i<data.length; i++) { eval(response[i]); } } Kind of weird to me... I'd understand if it read: function recv (data) { var response = eval("[" + data + "]"); for(var i=0; i<response.length; i++) { eval(response[i]); } } Andy, would you be so kind as to explain what you want to achieve ... Many, many thanks! Even more: I learned that JS goes into the for loop even if length is 0. So we might want to check or change the for loop... Cheers - Frank

3 3

[cells-devel] Re: [cells-gtk-devel] lots of circular cells in cells-gtk3?
by Ken Tilton 14 Apr '08

14 Apr '08

Peter Hildebrandt wrote: > Ken, did you change anything in cells as to how circular references > are dealt with? ps. while I am looking, look for a comment dated 2008-03-15 in cells.lisp k

2 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

cells-devel April 2008