But this time, you don’t have to download a snippet.
First, I know a lot of people don’t really understand what the phrase means; and in fact it can mean quite a few things. Really all it means is that they are dynamic menus of some sort. In this case, it takes the standard Drupal hierarchical menu structure, and modifies it so that when you click on a parent item, instead of going to that page it opens the menu beneath it. (This has a drawback; that page is now inaccessible, but it can be revived).
To actually see this in action: try the demo site http://dhtml.demo.logrus.com/.
To download the module, visit: http://drupal.org/project/dhtml_menu.
This version has been completely updated with jquery, and works under 5.0 -- I hear there is a jquery compatibility library for 4.7. If anyone knows about that, it ought to be fairly simple to create a 4.7 version using it, but I haven't looked into it.
Also, there is a hardcoded array in the module that needs to be brought into the UI. The array tells it what menu items to 'ghost'. What this means is that it creates a duplicate menu item for parent items that actually contain content. The best example is the 'Administer' page, which it does automatically. When you click Administer to open the admin menu, you will see a duplicate 'Administer' link right below it. Click on that one to get to the real menu.

Very nice. I see you
Very nice. I see you adjusted it to work (more) correctly without javascript.
What is the query load like for a large set of menus?
I've got a client who uses javascripty menus and with a large taxonomy, the load time for every page was painfully slow, because it had to query every menu item name/path/etc for building the fancy dropdown menu.
I only adjusted the demo to
I only adjusted the demo to have everything go to a unique location.
There's no query at all; menus are built from a cached array that has to be loaded anyway.
There is the cost that the entire menu tree has to be built as opposed to just the active tree (even without javascript on; it's built but hidden).
Great module
Wow... greate module... many thanks for you! :)
Does it support book menus?
I need book menu support like I had patched into ActiveMenu. Drupal 5 killed my patch.
Books aren't terribly well
Books aren't terribly well suited to DHTML menu because parents also have content; which means you pretty much have to 'ghost' every parent item automatically, which has its own problems. craq's double-click solution is ok but not fantastic.
Theoretically it oughtn't be that difficult to re-theme the book navigation to support it, but I never got far looking into it when I realized that it's not quite as good as menus.
adding a target="_blank" to a dhtml menu item?
i can't find a code snippet to do this in drupal 5
any chance you can help?
many thanks for all your awesome work on drupal.. :)
-shane
Wow, this looks like a great
Wow, this looks like a great menu system. I had been keeping most of my menus expanded but this makes it a lot easier to find stuff in the menu system quickly. Many thanks!
Any progress on Drupal 4.7 compatibility?
I'd like to consider using this for my Drupal 4.7 sites, but only if it's compatible. Any progress on this?
This module uses jquery and
This module uses jquery and so won't likely be available for 4.7; but if you do a search on my blog here, you'll see my older code which could be dropped in at the theme level. It's not as convenient and not as robust, but it works.
Post new comment