I've been playing with a driver for hu.dwim.perec, but I have a couple of 
questions and I'm hoping perhaps members of this group more familiar with the 
view machinery of weblocks might be able to point me in the right direction.  
I've based the driver more-or-less on the weblocks-elephant store, as that 
seems to be the closest match to what perec requires:  Dynamic transactions and 
(at least for now) the persistent-proxy mechanism.  

My issue is in getting updates and insertions to work properly.  I have very 
good results for all kinds of views (grids, forms, mixins etc) for objects that 
I manually populate my database with.  However I seem to be missing something 
crucial with regards to, say, updating a persistent-object from a drill down 
form.  After editing the form and clicking submit, the cancel button greys out, 
but the form does not disappear and the database is not updated.  Is there some 
extra customization required to something like a data-form-on-submit :after 
method?

Also, far less critical at the moment, I don't seem to be able to enable the 
checkbox column to select items from my grid edit.  I haven't spent much time 
on this, but I do specify :allow-select-p T when instantiating the widget.  Is 
something else required?

And finally, I originally had aspired to support the entity-relationship 
metaclasses as in hu.dwim.meta-model, which are really quite powerful, and add 
a kind of prototypal dynamism to the persistent-associations object-model (a 
little like an RDF store).  Unfortunately, from what I've seen it doesn't look 
like weblocks will accommodate that type of dynamism (at least without some 
additional help). Views, for example, would have to be dynamically recompiled 
when needed.  I'm not sure if this is even reasonable, and I'd have to study 
hu.dwim.metamodel a bit further to see where I might even find a hook to use 
for triggering such a thing.   This is a low priority, but I'm interested if 
there are any ideas out there for the weblocks side of the matter.

If anyone is interested in having a look at the existing weblocks-perec store 
driver code and weblocks-perec-demo code as it stands I created a fork on 
github:  http://github.com/danlentz/weblocks/

Thanks everyone,
Dan

-- 
You received this message because you are subscribed to the Google Groups 
"weblocks" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/weblocks/-/L8UfnJzIR2cJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/weblocks?hl=en.

Reply via email to