From ktilton at nyc.rr.com Tue Jan 10 22:11:47 2006 From: ktilton at nyc.rr.com (Kenny Tilton) Date: Tue, 10 Jan 2006 17:11:47 -0500 Subject: [cells-devel] Re: Cells: metaclass option not handled correctly ? In-Reply-To: <46EF24C9-2480-4B3D-BBFA-024D795CA2E2@prion.de> References: <46EF24C9-2480-4B3D-BBFA-024D795CA2E2@prion.de> Message-ID: <43C43123.4000201@nyc.rr.com> Frank Goenninger - PRION Consulting wrote: > Kenny, > > before posting to cells-devel I wanted to ask if it's only in my > cells 2.0 version that I have difficulties with something like: > > (defpackage :net.goenninger.sw.core > (:nicknames "NG.CORE") > (:use :common-lisp > :db.allegrocache > :cells) > (:export #:core)) > > (in-package :ng.core) > > (defmodel mvc-base () > ((model :cell :ephemeral :accessor model :initform nil) > (view :cell :ephemeral :accessor view :initform nil) > (controller :cell :ephemeral :accessor controller :initform nil)) > (:metaclass persistent-class) ;; <<-- > HERE !!! > ) > > Without modifying the defmodel macro I get some undefined generic > function error. With this modification > > .... in the defclass part of defmodel .... > > (:metaclass ,(or (cadr (find :metaclass options :key #'car)) ;; > Need to take the cadr of the find result !!! > 'standard-class))) Your fix looks right, thanks. btw, I started to look at AllegroCache and especially (+ Cells acache) but got sidetracked. Acache also sounded a little raw and pre-alpha based on exchanges with Foderaro. Let me know if you need help. kt From fgoenninger at prion.de Tue Jan 10 22:21:37 2006 From: fgoenninger at prion.de (Frank Goenninger - PRION Consulting) Date: Tue, 10 Jan 2006 23:21:37 +0100 Subject: [cells-devel] Cells and peristency? All cells or none - or? Message-ID: Hi all: I am currently trying to implement a persistency for a Cells-based app using AllegroCache (and OS X, ACL 7.0 Enterprise Edition). Now, I am not so sure if it makes sense at all to specify the persistency per model... Suppose I have a network of cells each being connected either via def- c-output or some other means and therefore depending on each other in their state. This is so because I figured I cannot re-load a valid overall state comprised by all cells in my app by just loading a few of the models from the DB. So, I think, there should be some general (meta-level) persistency that is inherent by all cells that have references to other cells. Now, as I see it, this needs some more tweaking of def-c-output, synapses and other means that link cells to ensure we get some knowledge of these links. This knowledge is then transformed into some code that defines the respective classes as persistant. Which leads to some new areas for me: Changing the metaclass of a class at runtime... Doable at all? Meaningful? Need to investigate... Any ideas or hints or solution attemps of youz guyz out there in space? Thanks for any comments. Frank From root at common-lisp.net Wed Jan 18 16:23:13 2006 From: root at common-lisp.net (root) Date: Wed, 18 Jan 2006 10:23:13 -0600 (CST) Subject: [cells-devel] Auto-nag: cells link verifier failed Message-ID: <20060118162313.B6C991904A@common-lisp.net> You are being nagged on because your project's name showed up in the nightly Checkbot run. Checkbot checks for broken links etc. This probably means that you are either pointing to a broken link or that someone is pointing to a broken link on your site. Or something else, it check's a bunch of stuff. Update your webpages or you shall be nagged again next week. To find out what's wrong with your webpages, please consult: http://common-lisp.net/checkbot/checkbot-common-lisp.net.html Any questions? You can reach the author of this cronjob at admin at common-lisp.net Thanks!