It seems lazy-navigation does not behave like navigation.
It does not show widget because we didn't enter url for which widget is
connected.
Using your code "/baz" and "/quux" uris work.
And using this code uris "/" and "/quux" work.
(make-navigation
"works with lazy-navigation"
(list "baz" (make-widget "baz widget") "")
(list "quux" (make-widget "quux widget") "quux")
:navigation-class
'lazy-navigation
)
This code just works with "/" uri and your code didn't.
четверг, 19 декабря 2013 г., 22:24:04 UTC+2 пользователь John Morrison
написал:
>
> Hi All;
>
> Probably PEBKAC (problem exists between keyboard and chari), but I was
> trying to get protected navigation to work, based upon the ancient advice
> to use a subclass of lazy-navigation. In trying to debug it, it turns out
> I am unable to get lazy navigation to work at all. Here's the offending
> code from a standalone webapp. I tried some obvious things like providing
> f-underscore function widget generators instead of instantiated string
> widgets, etc., to no avail. Would appreciate being pointed in the right
> direction. Hopefully the attached file is more readable than the
> cut-and-paste job below...
>
> Was also unsure why protected navigation necessitates lazy navigation.
> Perhaps there is some safety in not generating widgets that should not be
> shown to the unauthorized user...
>
> Thanks in advance,
>
> -jm
>
> (defun init-user-session (root)
> (setf (widget-children root)
> (list
> (make-navigation
> "this works"
> 'foo (make-widget "foo widget")
> 'bar (make-widget "bar widget"))
> (make-navigation
> "works with vanilla navigation. fails 404 if using lazy-navigation"
> 'baz (make-widget "baz widget")
> 'quux (make-widget "quux widget")
> :navigation-class
> #-NIL 'lazy-navigation ; fails with 404
> #+NIL 'navigation ; works
> )
> (lambda (&rest args)
> (with-html
> (:strong "Happy Hacking!"))))))
>
>
--
You received this message because you are subscribed to the Google Groups
"weblocks" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/weblocks.
For more options, visit https://groups.google.com/groups/opt_out.
