The company I work for used this before I started. The generated code by this thing is extremely terrible and takes up WAY too much space for what it does.. Programming a generated menu like this was such a pain.
A nested UL or OL for a menu is much easier to work with, offers a great hierarchy if for whatever reason your css isn't supported (some hand held devices), and it's semantic.
I've created literally hundreds of menus over the past couple of years. The best advice I could give is to stick with straight css/html. My latest menu uses 15 lines of css, and then the html for however deep the menu structure needs to go. I'm sure you can imagine how good that is on your server loads.
Then if the client wants animated dropdowns, and a timer on it (this is pretty big, because straight up css :hover elements lose the drop down the split second you mouse off of it) then I use jQuery and a few additional lines of js.
It's a much better approach than using SoThink, so if any of you are looking into it, then perhaps you should give Mr. UKBusinessLive some of his first business and get a much more effective drop down navigation.
01-27-2009, 12:31 PM
Threaded Mode