"Leslie P. Polzer" <[email protected]> writes: > On Sep 8, 6:33 am, John Fremlin <[email protected]> wrote: > >> According to the AMOP, slot-definition-readers only applies to >> direct-slot-definitions not effective-slot-definitions. > > Good to have that sorted out. OP: could you produce a self-contained > Weblocks test case that exhibits the problem?
Not really. The problem happens when using the Cells library with Weblocks. I had initially suspected that this was the case, but then when I started reading the weblocks code, I misread class-direct-slots as class-slots, masking the problem with the Cells library and leading to the problem I asked about. In case anyone else comes across this in the future, if you want to use Cells with Weblocks you'll want to modify the defmodel macro slightly. Remove the block where the :accessor/:reader/:writer properties are removed from the slot specifications, because otherwise weblocks will think that all the slots should be hidden when it creates your views. You'll also want to extend class-visible-slots-impl so that the slots added by the Cells library don't show up in the UI. There other (pretty complicated) things that I want to do to integrate them more fully, but if I get around to them then I'll post about them then. db48x --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. 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 -~----------~----~----~----~------~----~------~--~---
