I know this is very low-tech, but I just arrange my links into a nav-looking
structure. Since they will auto-disable if they link to self (same page),
they form a kind of menu where you can see where you are. This has been
good enough for most of what I do, without hardly any coding (as a result of
auto-links).
Jon
Robert Novotny wrote:
>
> I have tried to use dropdown menu in one of my projects. NavMenu has been
> broken in that time (and I didn't figure out how to patch it) and my
> effort in integrating TigraMenu wasn't succesfull either. Finally I have
> used the approach which uses a pure CSS menu which is based on the :hover
> class. The menu is composed of multiple nested <span> tags (which are
> mapped to Wicket Label-s or Link-s). However, this approach requires you
> to know the structure of the menu beforehand and may pose a limitation
> when you require menu items which changes at runtime dynamically.
>
> (There was another slight glitch: in IE this approach requires
> css-hover.htc script, which may be disabled on some browsers due tu
> security reasons).
>
> However, this approach has suited me well.
>
>
> Eelco Hillenius wrote:
>>
>> The big question there is whether you know all items beforehand or
>> not. If yes, integrating with any javascript library is easy. If not,
>> you need a tree, and probably can best look at that component or
>> navmenu
>> (https://svn.sourceforge.net/svnroot/wicket-stuff/branches/wicket-1.3/wicket-contrib-navmenu)
>> which is deprecated (won't be supported) but nevertheless may give you
>> an idea.
>>
>> The second big question is: what are you going to do with these items:
>> component replacements or do links point to bookmarkable pages?
>>
>> I'd really love to see someone contribute a nice component for this
>> based on bookmarkable pages and a tree. navmenu was a step in that
>> direction, but the API is't great.
>>
>> Eelco
>>
>>
>> On 3/7/07, Thomas R. Corbin <[EMAIL PROTECTED]> wrote:
>>>
>>> We need a menu bar across the top of our pages, with pull down menus.
>>>
>>> We used to use this stuff:
>>> http://struts-menu.sf.net
>>>
>>> but I'm not sure how to integrate it, since it seems to rely on jsp
>>> tags.
>>>
>>> Thanks.
>>>
>>> -------------------------------------------------------------------------
>>> Take Surveys. Earn Cash. Influence the Future of IT
>>> Join SourceForge.net's Techsay panel and you'll get the chance to share
>>> your
>>> opinions on IT & business topics through brief surveys-and earn cash
>>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>>> _______________________________________________
>>> Wicket-user mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/wicket-user
>>>
>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share
>> your
>> opinions on IT & business topics through brief surveys-and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Wicket-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/wicket-user
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/What%27s-the-best-way-of-doing-menus-in-Wicket--tf3366440.html#a9371865
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
