Divia wrote:
>
> Thank you so much for this incredibly helpful response. I've been
> struggling with trying to get the dispatcher work (and I am still
> using the old nav system).
You're welcome!
> The error I've been getting has been
>
> SIMPLE-ERROR: There is no class named CONTENTREES::DISPATCHER.
> (contentrees is the name of my app)
>
> [...]
>
> I tried using 'hunnchentoot::dispatcher instead, but that didn't seem
> to work either.
No, the dispatcher class I was referring to should be supplied by
Weblocks.
What version of Weblocks are you using (or upload your tree
somewhere)?
Looks like yours is *very* old. :)
> I've been reading the navigation code, and while I definitely
> understand it better than I did before, I can't figure out what I'm
> doing wrong. Any tips would be extremely helpful, but if you think
> the new navigation is stable enough that I should just upgrade to
> that, then maybe it makes more sense for me to do so and invest any
> further effort in understanding that code.
The new navigation is pretty stable apart from one bug which
isn't solved yet. This bug only affects you if you're trying
to swap in a navigation in an AJAX request:
;; example 1
(with-flow (root-composite)
(yield (make-login ...))
(yield (make-navigation ...)))
;; example 2
(render-link (lambda (&rest args)
(setf (composite-widgets my-composite)
(list (make-navigation ...))))
"Nav it")
If you're not doing anything like this then I suggest
upgrading to the latest -dev.
Otherwise I'll help you getting your work done with
the version of Weblocks you are using right now.
Cheers!
Leslie
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
