On Mon, Nov 2, 2009 at 12:25 PM, Vesa <[email protected]> wrote:
>
> Hi,
>
> I have a feeling that SiteMap is a common cause of frustration among
> newbies and was wondering why is it so? Having visible menu entries
> generated by default on controlled pages made me feel that the
> framework is making too many assumptions. I would personally prefer
> having to explicitly make pages as menu items or make some kind of
> distinction between access control and menus. Is it so common case
> that this is the best thing to do and I just don't realize yet how
> much easier my life is with SiteMap?
>
So, if you've got access control and menus separated, then you have to
coordinate them somehow or your users will be cranky ("I clicked on this
link and got a nasty error message... why show me the link if I can't access
it?") So, SiteMap is a single, unified declaration of site structure and
access control. If you don't want to use it, you can remove the single line
in Boot that sets the sitemap. Without that line, you can access any page
and do anything.
>
> - Vesa
> >
>
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Lift" 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/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---
