Generic Navigation Panel
Hi I'm creating a new website with wicket which should have a normal navigation bar. I'd like to be able to detect whether a link points to the current page to give the surrounding div a special class. For example on page1: div class=activeLink a href=page1page1/a /div div a href=page2page2/a /div I thought about autolinking which does that automatically, except it adds very ugly spanem tags. I also don't want to change this globally just to have a nicer navigation autolinking going. In addition this would be tricky as I need the divs around the links, but with different CSS classes. I'm thinking about creating a panel (representing the div with the link) which then adds the link and which has to be created by giving the current page via the constructor in order for it to find out if the link represents the current page. But this seems to be very complicated so I think there must be a more elegant solution for that, as this requirement surely isn't anything new?! Thanks for your hints Matt -- matthias.kel...@ergon.ch +41 44 268 83 98 Ergon Informatik AG, Kleinstrasse 15, CH-8008 Zürich http://www.ergon.ch __ e r g o nsmart people - smart software smime.p7s Description: S/MIME Cryptographic Signature
Re: Generic Navigation Panel
You can actually configure the tags that are put around a disabled link at application level, like this: getMarkupSettings().setDefaultBeforeDisabledLink( ); getMarkupSettings().setDefaultAfterDisabledLink( ); This would give span*linktext*/span for disabled lnks (such as an autolink to the current page). Matthias Keller wrote: Hi I'm creating a new website with wicket which should have a normal navigation bar. I'd like to be able to detect whether a link points to the current page to give the surrounding div a special class. For example on page1: div class=activeLink a href=page1page1/a /div div a href=page2page2/a /div I thought about autolinking which does that automatically, except it adds very ugly spanem tags. I also don't want to change this globally just to have a nicer navigation autolinking going. In addition this would be tricky as I need the divs around the links, but with different CSS classes. I'm thinking about creating a panel (representing the div with the link) which then adds the link and which has to be created by giving the current page via the constructor in order for it to find out if the link represents the current page. But this seems to be very complicated so I think there must be a more elegant solution for that, as this requirement surely isn't anything new?! Thanks for your hints Matt - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Generic Navigation Panel
cant you use PagingNavigator? -igor On Wed, Jul 22, 2009 at 7:05 AM, Matthias Kellermatthias.kel...@ergon.ch wrote: Hi I'm creating a new website with wicket which should have a normal navigation bar. I'd like to be able to detect whether a link points to the current page to give the surrounding div a special class. For example on page1: div class=activeLink a href=page1page1/a /div div a href=page2page2/a /div I thought about autolinking which does that automatically, except it adds very ugly spanem tags. I also don't want to change this globally just to have a nicer navigation autolinking going. In addition this would be tricky as I need the divs around the links, but with different CSS classes. I'm thinking about creating a panel (representing the div with the link) which then adds the link and which has to be created by giving the current page via the constructor in order for it to find out if the link represents the current page. But this seems to be very complicated so I think there must be a more elegant solution for that, as this requirement surely isn't anything new?! Thanks for your hints Matt -- matthias.kel...@ergon.ch +41 44 268 83 98 Ergon Informatik AG, Kleinstrasse 15, CH-8008 Zürich http://www.ergon.ch __ e r g o n smart people - smart software - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Generic Navigation Panel
Any plans to move this down to the Component level? I've had situations where I needed to override this at the page level and even within a panel within a page.. John- On Wed, Jul 22, 2009 at 7:14 AM, Iain Reddickiain.redd...@beatsystems.com wrote: You can actually configure the tags that are put around a disabled link at application level, like this: getMarkupSettings().setDefaultBeforeDisabledLink( ); getMarkupSettings().setDefaultAfterDisabledLink( ); This would give span*linktext*/span for disabled lnks (such as an autolink to the current page). Matthias Keller wrote: Hi I'm creating a new website with wicket which should have a normal navigation bar. I'd like to be able to detect whether a link points to the current page to give the surrounding div a special class. For example on page1: div class=activeLink a href=page1page1/a /div div a href=page2page2/a /div I thought about autolinking which does that automatically, except it adds very ugly spanem tags. I also don't want to change this globally just to have a nicer navigation autolinking going. In addition this would be tricky as I need the divs around the links, but with different CSS classes. I'm thinking about creating a panel (representing the div with the link) which then adds the link and which has to be created by giving the current page via the constructor in order for it to find out if the link represents the current page. But this seems to be very complicated so I think there must be a more elegant solution for that, as this requirement surely isn't anything new?! Thanks for your hints Matt - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Generic Navigation Panel
it is on component level. abstractlink has those methods i believe. -igor On Wed, Jul 22, 2009 at 10:16 AM, John Armstrongsiber...@siberian.org wrote: Any plans to move this down to the Component level? I've had situations where I needed to override this at the page level and even within a panel within a page.. John- On Wed, Jul 22, 2009 at 7:14 AM, Iain Reddickiain.redd...@beatsystems.com wrote: You can actually configure the tags that are put around a disabled link at application level, like this: getMarkupSettings().setDefaultBeforeDisabledLink( ); getMarkupSettings().setDefaultAfterDisabledLink( ); This would give span*linktext*/span for disabled lnks (such as an autolink to the current page). Matthias Keller wrote: Hi I'm creating a new website with wicket which should have a normal navigation bar. I'd like to be able to detect whether a link points to the current page to give the surrounding div a special class. For example on page1: div class=activeLink a href=page1page1/a /div div a href=page2page2/a /div I thought about autolinking which does that automatically, except it adds very ugly spanem tags. I also don't want to change this globally just to have a nicer navigation autolinking going. In addition this would be tricky as I need the divs around the links, but with different CSS classes. I'm thinking about creating a panel (representing the div with the link) which then adds the link and which has to be created by giving the current page via the constructor in order for it to find out if the link represents the current page. But this seems to be very complicated so I think there must be a more elegant solution for that, as this requirement surely isn't anything new?! Thanks for your hints Matt - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Generic Navigation Panel
Good info, thanks Igor, I'll check it out. J On Wed, Jul 22, 2009 at 10:27 AM, Igor Vaynbergigor.vaynb...@gmail.com wrote: it is on component level. abstractlink has those methods i believe. -igor On Wed, Jul 22, 2009 at 10:16 AM, John Armstrongsiber...@siberian.org wrote: Any plans to move this down to the Component level? I've had situations where I needed to override this at the page level and even within a panel within a page.. John- On Wed, Jul 22, 2009 at 7:14 AM, Iain Reddickiain.redd...@beatsystems.com wrote: You can actually configure the tags that are put around a disabled link at application level, like this: getMarkupSettings().setDefaultBeforeDisabledLink( ); getMarkupSettings().setDefaultAfterDisabledLink( ); This would give span*linktext*/span for disabled lnks (such as an autolink to the current page). Matthias Keller wrote: Hi I'm creating a new website with wicket which should have a normal navigation bar. I'd like to be able to detect whether a link points to the current page to give the surrounding div a special class. For example on page1: div class=activeLink a href=page1page1/a /div div a href=page2page2/a /div I thought about autolinking which does that automatically, except it adds very ugly spanem tags. I also don't want to change this globally just to have a nicer navigation autolinking going. In addition this would be tricky as I need the divs around the links, but with different CSS classes. I'm thinking about creating a panel (representing the div with the link) which then adds the link and which has to be created by giving the current page via the constructor in order for it to find out if the link represents the current page. But this seems to be very complicated so I think there must be a more elegant solution for that, as this requirement surely isn't anything new?! Thanks for your hints Matt - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
