Some of us have taken that nav class out of the tag, set it up to run in a JSP 
scriptlet, and included the JSP in place of the tag. My version has two extra 
methods. One reads the webapps security constraints, the other gets the users 
roles. Then if the user doesn't have access to a resource, he doesn't get the 
link.

http://www.magnolia.info/wiki/Wiki.jsp?page=AutoNavigationClassWithProtectedMode

I haven't gone through the taglib tutorial yet, but I'm sure its not hard to 
put it all back into a tag.

So if you don't feel like dealing with building a custom tag, you might get 
some ideas on building a nav tree from my include file scriptlet.

I fooled around a lot with vertical & horizontal CSS cascading menus. The 
trickiest one is like an M$ menu with different icons.

http://www.ahouse4you.org/css_menu/


-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 06, 2006 1:46 AM
To: [email protected]
Subject: Re: [magnolia-user] experience with building custom navigations

Hello Thomas,

Thanks for the input. I am currently going in the direction of tweaking the 
simplenavigation using css. However I think I will try the custom tag thingy, 
as it sounds more flexible to me.

Is there a tutorial or howto somewhere, briefly describing how to create a 
custom tag for magnolia?

Cheers

Claudio

***********************************************
Ingenieurbüro Philipp Hungerbühler IPH
Herr Claudio Greuter
Lagerhausstrasse 9
8400 Winterthur
Tel: +41 (052) 233 94 72
Fax: +41 (052) 233 94 71
[EMAIL PROTECTED]
***********************************************

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 6. April 2006 10:16
To: [email protected]
Subject: Re: [magnolia-user] experience with building custom navigations

I did a similar thingie by using the headerImage in normal magnolia page 
properties.

Instead of using the image in the header, you can potentially use it anywhere 
else in the page (or modify the template to get additional fields, like 
menuImage, bottomImage, etc - see the templating tutorial for this).

If you want to generate a whole menu, I think you should make your own version 
of the simplenavigation tag. You don't have to change the source, make your own 
custom tag instead (tricky if you don't know how to make custom tags, but 
doable).

When iterating through the root pages (the 1. level nodes), collect the image 
property as you go along, and smack it into the menu.

On 4/6/06, Claudio Greuter <[email protected]> wrote:

> What I would like to do:
> - Show an image and or the page title
> - To be able to set the displayed image using the page properties (as 
> an editor)
>

----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to