Aron,
This looks like good stuff. The best way to get this added to the project is to:
1. Download the source from CVS and add your tag in. 2. Provide an example in the sample application. 3. Write documentation in the xdocs directory. 4. Create a patch and submit it to the bug tracker.
I can help with editing #3.
If you don't know how to create a patch, I can provide details on that - or you can just zip up the modifed project and send it to me via dropload.com. If you do this, the important part is making your changes in a CVS version of the project so I can see what's changed.
Thanks,
Matt
On Feb 8, 2005, at 2:22 PM, Scott Sayles wrote:
Hey Aron,
Sounds interesting. Unfortunately, at this point, I have little to do with StrutsMenu. I just don't' have the time. Matt has been the one heading things up recently. I'll copy you to the user list as well.
Thanks,
Scott
-----Original Message----- From: Aron Gombas [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 08, 2005 3:51 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: CrumbsTag idea
Hi Scott!
First, sorry for my poor English. We're using the struts-menu package in a current project, and I had the idea that I'd use it also for generating a "crumbs control", because both the title keys and the URL's are available in menu-config.xml, and I don't really need anything else for the crumbs.
First, I thought I'd use the VelocityMenuDisplayer with some tricky macros to render my menu to a format like "link1 > link2 > link3", but then I had to realize that I can't pass in an arbitrary list of links to the existing DisplayMenuTag, I can pass only a menu. So I had the choice to: a - create a dummy menu to each page (each configuration of links) and render it with Velocity b - implement a separate tag which would receive the list of links as attrib and use the MenuRepository object from the session-scope
I decided to do b, to have the following syntax (as you see I needed to support EL):
... <wasp:crumbs links="menu.home, menu.domains, buildingStructureTypeList. title, ${titleKey}"/> ...
The tag class evaluates and breaks up the "links" attib, and builds the HTML from the localized resource strings plus the URL's generated by struts-menu. Not a big deal, but works perfectly and hyper-lightweight, and you can actually improve it to a real general tag: - now the formatstrings are just hard-wired to the .java, but you can easily externalize them to some .properties file (as I plan to do that later) - also, getting the resources is Struts-dependent, so you might want to make changes in order to make it framework-independent - adding extra attribs like e.g. "class" to make it look more standard is also a good idea
It's really just half-made, not more than an idea. I thought you might be interested in this. Plz ignore my todo-tags in Hungarian. ;) Thanks for reading.
Aron Gombas 3NF Corporation www.3nf.com
PS. I'm not subscribed to the devel-list, so plz write me directly if you needed to communicate with me.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
struts-menu-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/struts-menu-user
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ struts-menu-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/struts-menu-user
