[Seaside] Navigation in Seaside

Philippe Marschall philippe.marschall at gmail.com
Thu Apr 10 17:01:52 UTC 2008

2008/4/9, Vyacheslav Akhmechet <coffeemug at gmail.com>:
> Hi Lukas,
>  On Tue, Apr 8, 2008 at 2:09 AM, Lukas Renggli <renggli at gmail.com> wrote:
>  >  sorry for not replying such a long time.
> It's no rush :)
>  >  We do not do have the "friendly URL system" though. Just out of
>  >  curiosity: How do you handle conflicts in the URL, when multiple
>  >  navigation widgets appear on the same page?
> At the moment we don't. If someone adds more than one navigation at
>  the same depth level on the widget tree, the behavior is undefined.
>  We're refactoring the navigation widget so we're trying to figure out
>  how to solve this problem. I think the best option so far is to allow
>  only one navigation widget per depth level to consume URI tokens.
>  >  I don't see anything wrong with the design
> That's probably because you don't map the component to URLs. If you
>  did, you'd encounter the problem you mentioned above. Another problem
>  is temporarily replacing the root of the tree with a "dialog" page
>  that's later expect to return by invoking a continuation. The problem
>  with doing this is that when I replace the root, the navigation
>  widgets are gone and the URL the user is at (/foo/bar) becomes
>  invalid, so the server sends a 404. One way to solve this is to
>  temporarily redirect to '/', but this seems somewhat hackish.
>  I wanted to get an idea of what Seaside folks think about these issues.

We don't do automatic URL management so we don't have such problems.
Really, the problems outlined here very basic and just the tip of the


More information about the seaside mailing list