On 6/16/06, Nikolaos Abatzis <[EMAIL PROTECTED]> wrote: > Hi, > > The call oCMenu.makeStyle is no longer needed per the coolmenu4 web site and > corresponding tutorial for migration from coolmenu3 to coolmenu4 (see > www.dhtmlcentral.com/projects/coolmenus/tutorials.asp?id=9). > > Struts-menu seems to be oblivious to that fact and it generates the call which > causes a javascript error right before the call to oCMenu.construct(), which > prevents the menu from being constructed.
That's my fault - sorry. However, I've used CoolMenus on a couple of different projects and never had an issue with this. > > Does anyone else have come across this and found a solution. Struts-menu has > been quite cumbersome to use and the hours spend debugging it seems too high a > price to pay for its benefit!!!! CoolMenus4 (and 3) seem pretty broken to me, so I don't know if I'd blame Struts Menu. I've recently migrated to the new CSS-only menus in 2.4. http://demo.raibledesigns.com/struts-menu/cssVertical.jsp > > After going to version 2.4 had a lot of problems with parsing menu-config and > I > have to use velocity.jar even though I do not use any of the velocity > displayers. It just does not seem to be very robust. Any assistance is greatly > appreciated. 2.4 should be backwards compatible with 2.3 (as far as menu-config.xml) and shouldn't require Velocity if you're not using a VelocityDisplayer. Do you have a stack trace that shows the issues you're having? Matt > > Regards > > Nikolaos > > > > _______________________________________________ > struts-menu-user mailing list > struts-menu-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/struts-menu-user > _______________________________________________ struts-menu-user mailing list struts-menu-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/struts-menu-user
