On Wed, Oct 14, 2009 at 5:07 PM, Markus Kolb wrote:
>
> On Oct 14, 10:36 pm, David Pollak
> wrote:
>
> > Are you talking about dynamic pages as part of a content management
> system
> > or are you talking about .html files appearing in the filesystem?
>
> It is comparable with a CMS.
> The inform
On Oct 14, 10:36 pm, David Pollak
wrote:
> Are you talking about dynamic pages as part of a content management system
> or are you talking about .html files appearing in the filesystem?
It is comparable with a CMS.
The information for building the SiteMap is available via API of
another library
On Wed, Oct 14, 2009 at 11:08 AM, mkolb wrote:
>
> On Oct 12, 7:29 pm, David Pollak
> wrote:
> > To address the specific issue of CondHidden/IfHidden, if a Loc (menu
> > location) fails the If() or Unless() test, it will not be
> > displayed/rendered/visible to the user. So, there's no need for
On Oct 12, 7:29 pm, David Pollak
wrote:
> To address the specific issue of CondHidden/IfHidden, if a Loc (menu
> location) fails the If() or Unless() test, it will not be
> displayed/rendered/visible to the user. So, there's no need for a IfHidden
> or a CondHidden LocParam.
>
> More broadly, Si
To address the specific issue of CondHidden/IfHidden, if a Loc (menu
location) fails the If() or Unless() test, it will not be
displayed/rendered/visible to the user. So, there's no need for a IfHidden
or a CondHidden LocParam.
More broadly, SiteMap represents all the pages in your site and the
v
Dave writes:
[...]
> Specifically, since both of my user types extend MegaProtoUser, I end
> up with loggedIn_? function that tells if some user is logged in, but
> is confused about which. So if a user of type 1 logs in and I call
> UserType2.loggedIn_?, it will also return true. Is there a
"marius d." writes:
> First of all I'm not reinventing anything. I don't think that If
> LocParam semantic is giving you the hidden functionality as well.
I haven't checked closely, but the scaladoc seem to indicate that it
does. And in my own menu snippets (which is based on the original menu
First of all I'm not reinventing anything. I don't think that If
LocParam semantic is giving you the hidden functionality as well. User
type 2 should not even see the menus for user type 1, not only to not
be able to access those locations.
The way I see it this functionality should be totally ir
Marius-
Thanks for your help on this. I guess I'm not sure how this differs
from the current conception of the If LocParam. As I understand it, it
is checked when determining what to display on the Menu as well as
when a User attempts to access the page (or its subdirectory if
passing a pair).
Yes, a Loc accepts many LocParams ... as I said above If/Unless/Test
would be used in conjunction with CondHidden to also provide
accessibility constraints.
Here is the definition
case object CondHidden(test: () => Boolean) extends LocParam
but we also have case class If(test: () => Boolean, fa
Hi Marius,
Thanks for the response. The LocParam is a good idea, but here is the
attendant problem. No only do I have to hide options A,B,C from user
type 2, I have to make sure user type 2 does not access those pages/
areas. Can I include that in the locParam as well? Right now, I'm
using an
Oh I should have read more carefully. Sorry Marius. Do you think you
could provide an example with dummy's as to how one of these
CondHidden and If's might work in conjunction?
Thanks,
Dave
On Oct 11, 2:54 am, "marius d." wrote:
> So doesn't what I described about help you? ... a conditional
So doesn't what I described about help you? ... a conditional Hidden
LocParam? ...thus the SiteMap contains all A, B, C, D, E, F menus but
for user type 1 D, E,, F are hidden, and for user type 2 A, B, C are
hidden. The decision would done in the function that you provide to
CondHidden.
If this h
Hi all-
I am interested in a similar question. I have two types of users and
once logged in, I'd like to provide them with distinct menu options.
For instance User type one would have a menu with A / B / C and User
Type Two would have D / E / F. I have tried a variety of approaches
including st
Well SiteMap is per LiftRules which means it's per application
runtime. One approach would be to define the entire SiteMap but
depending on the context using some conditional Hidden LocParam.
Perhaps something like:
case object CondHidden(coond: () => Boolean) extends LocParam
This could be used
15 matches
Mail list logo
