incubator-adffaces-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sonja Löhr <sonjalo...@arcor.de>
Subject RE: MenuModel issues
Date Mon, 09 Oct 2006 10:16:26 GMT

Thanks, Steve, I already took them from base-desktop.xss and it works.  

> -----Original Message-----
> From: Steve Vangasse [mailto:steve@boardshop.co.uk] 
> Sent: Montag, 9. Oktober 2006 12:02
> To: adffaces-user@incubator.apache.org
> Subject: Re: MenuModel issues
> 
> If you dig around in the trinidad code you should find the 
> new css selectors. Since I'm not using panelPage tabs and 
> menu bar at the moment I haven't got them to hand.
> 
> Steve Vangasse
> 
> Boardshop.co.uk - Board Sports Equipment and Clothing for the 
> UK and Europe www.boardshop.co.uk 0870 0600 688
> 
> 
> 
> ----- Original Message -----
> From: "Sonja Löhr" <sonjaloehr@arcor.de>
> To: <adffaces-user@incubator.apache.org>
> Sent: Monday, October 09, 2006 10:24 AM
> Subject: RE: MenuModel issues
> 
> 
> > Hi, Günther and Steve!
> >
> > Thank you very much for your tips!
> >
> > In the meanwhile I played around with the aliasList and it 
> had indeed some
> > effect - on the starting page at least ;-).
> >
> > In some document I also found a recommendation that the 
> navigation-rules
> > also shoult reflect the very same thing, such that I should 
> multiplicate 
> > my
> > navigation-cases for each submenu (most of them were mapped to "*").
> >
> > But do you really see any abstraction or even 
> simplification if we specify
> > view-ids over and over again to get any possible state of the app 
> > displaying
> > the right menu options? Since I'm using Facelets I had 
> > subtemplate-specific
> > menu parts anyway (before trying trinidad), so it is just about the
> > "selected" style for me.
> >
> > When I'll have successfully explored all the other 
> interesting components,
> > I'll return to the menus, perhaps things will have changed 
> completely in 
> > the
> > meanwhile ;-)
> >
> > @Steve:
> > As you see in my other post, there is also an issue 
> concerning skinning: 
> > The
> > <tr:panelPage> Menu-Facets use new CSS-selectors whereas 
> with <tr:page> 
> > you
> > get the "old" (??) selectors ...
> >
> > Greetings !
> >
> > sonja
> >
> >
> >
> >
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: Günther, Thorsten [mailto:Thorsten.Guenther@medocino.de]
> >> Sent: Montag, 9. Oktober 2006 10:07
> >> To: adffaces-user@incubator.apache.org
> >> Subject: AW: MenuModel issues
> >>
> >> Hi Sonja,
> >>
> >> I assume the "vanishing" problem you describe is exactly what
> >> you need the aliaslist for. The menue model can't know what
> >> branch of the tree to open if the current page is not part of
> >> the tree. So you give aliases to pages that should not
> >> display in any menue but should (keep) open a branch of the tree.
> >>
> >>         <value>/components/page_p1.jspx</value>
> >>         <value>#{navItem_a2b1.viewId}</value>
> >> = if /components/page_p1.jspx is displayed show the menue as
> >> if element navItem_a2b1 was displayed
> >>
> >>
> >> As for global menue: I find that a bit wired too. My solution
> >> is to have a hidden (not rendered) element be the root for my
> >> logical top-level menue at level 2. Drawback is that the
> >> branch containing my top-level menue is left when the user
> >> clicks on "help". You have to provide a link on the help-page
> >> to allow the user to get back to the main application.
> >>
> >> Regards,
> >> Thorsten
> >>
> >> -----Ursprüngliche Nachricht-----
> >> Von: Sonja Löhr [mailto:sonjaloehr@arcor.de]
> >> Gesendet: Sonntag, 8. Oktober 2006 13:04
> >> An: adffaces-user@incubator.apache.org
> >> Betreff: MenuModel issues
> >>
> >>
> >> Hi, all!
> >>
> >> My first post - on my third day to trinidad.
> >> I already read that I'm not the only one not understanding
> >> the MenuModel
> >> stuff ...
> >> My <tr:page> opens a submenu when I click a parent menu
> >> element, but if I'm
> >> going further down in the hierarchy, all submenus vanish again?
> >> Did someone understand what to do whith that "aliaslist" from the
> >> example-faces-config?
> >>
> >> And: Why is the "global menu" the root of the model
> >> hierarchy? Is there any
> >> possibility to "start" the hierarcy in, say, the
> >> navigation1-facet? There
> >> are some links I would like to have as "globalMenu", but 
> these are no
> >> starting points for navigating the hierarchy but merely things like
> >> "logout", "help", ....
> >>
> >> VERY confusing ....
> >>
> >> Thanks for any hints, suggestions or samples!
> >>
> >> sonja
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
> > 
> 
> 



Mime
View raw message