Hi! I do use tr:page with a MenueModel configured by MenuModelAdapter stolen from the demo. The tr:page is sitting in a Facelets template, so I only provide the content area and as needed some tr:page-facets in the client-pages. I agree that using the global buttons as root of the MenueModel is not ideal. As a workaround I do not render the global button that is the root of the applications menu hierarchy. The visible top-level items in the MenueModel like "Help" point to single pages which have "back" links to pages in the standard menu hierarchy in their content areas.
I would also like to hear how you other users create and display their menus. Regards, Thorsten Günther -----Ursprüngliche Nachricht----- Von: d sanders [mailto:[EMAIL PROTECTED] Gesendet: Sonntag, 12. November 2006 00:35 An: [email protected] Betreff: Anyone working on NavigationPane/MenuModel? Just checking to see if anyone is working on NavigationPane/MenuModel (i.e. in a panelPage). How are people doing navigation right now? Page does not work (global buttons are treated as root of nav tree rather than a path into the nav tree), and panelPage does not work with MenuModel. Is everyone doing their testing without MenuModel? ____________________________________________________________________________________ Yahoo! Music Unlimited Access over 1 million songs. http://music.yahoo.com/unlimited
