All three of the links allow "roles" to be specified in menu-config.xml - this is how the roles are used. For an online example, see:
http://raibledesigns.com/struts-menu/rolesMenu.jsp The "dhtml" menus use ListDisplayer, not DropDownDisplayer, so you're right in that it's not in that one. The IE6 problem is b/c the dhtmlDropDown does not currently support nested children > 2. Care to donate your cookie code? One enhancement I was thinking of for struts-menu was to make an XSLDisplayer that uses XSL on the menu-config.xml file to change the menus. It might be a lot of work, who knows until I get into it. The idea would be that there would be default XSL files for all menus, and then I'd add a path attribute to the tag library so users could customize there own. Thoughts? Anyone know how to read an XSL file from a JAR file? Matt > -----Original Message----- > From: Edgar P. Dollin [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 12, 2003 6:30 AM > To: 'Matt Raible' > Cc: 'Struts Users Mailing List' > Subject: RE: StrutsMenu > > > Matt: > > The links below don't seem to do any role stuff that I can find. BTW: > there are some bugs in the dhtmlDropdown.jsp with IE6. > > Maybe I am reading the code incorrectly but the DropDown > displayer never > calls isAllowed or works with an object that does The coolmenu > displayer does makes calls although it's structure is a tad different > than the drop down. I have started doing the analysis of where to put > the checks to enable the role/permission implementation. > > The tree menu link is really interesting. The guy and his bud's are > really good. > > BTW: I reworked the cookies and got the menu's to act > consistently from > page to page. > > Thanks again > > Edgar > > -----Original Message----- > From: Matt Raible [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 11, 2003 9:35 PM > To: Edgar Dollin > Cc: 'Struts Users Mailing List' > Subject: RE: StrutsMenu > > > > It should already be built into the following Displayers using the > "roles" attribute on a menu or item. > > http://raibledesigns.com/struts-menu/dhtmlDropdown.jsp > http://raibledesigns.com/struts-menu/dhtmlExpandable.jsp > http://raibledesigns.com/struts-menu/coolmenu4.jsp > > For saving a menu's expanded location - you might want to look at the > following Tree menu. I hope to add support for this type of > menu in the > coming weeks. > > http://webfx.eae.net/dhtml/xtree/demo.html > > HTH, > > Matt > > -----Original Message----- > From: Edgar Dollin [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 11, 2003 6:04 PM > To: '[EMAIL PROTECTED]' > Cc: 'Struts Users Mailing List' > Subject: StrutsMenu > > > Would it be simple to implement roles and permissions on the > DropDownDisplayer? I have started to look at it and am not > sure of all > the touch points. > > BTW: my solution for restoring a menu position on a target > page with the > same menu as the prior page is sub-optimal. The only solution I could > come up with saved menu down and up movements and created expiring > cookies on menu selection. Of course if you do any other action the > menu doesn't redrop. If you are using contexts, the cookies are > discarded across the change of context. It looks like the only way to > really make menu position controllable is to do some server > side stuff. > An interesting project. > > Thanks for your help. > > Edgar > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
