Duplicating functionality

One thing that would make me use this module over DHTML menu: active menu handles book navigation the way I want it to. The parent book link (for active menu) is a link to the parent node, not simply an expanding menu item with the parent book title repeated twice (DHTML menu). Also, if I want collapsible blocks, the Jstools module does double duty (I'm trying not to have too many modules installed on my site, so "Advanced Book Block" and DHTML menu, which duplicate each other to some degree, can be replaced by active menu). There is at least a need to add some settings for DHTML menu so that it has some of the features of this module, if I would vote for retiring active menu. My two cents. It would be great, since the functionality is so similar, if everyone working on these menu-enhancement modules could work with a common tool set and really benefit from collaboration. What are the advantages of not having any javascript? Does active menu degrade gracefully?

Hi!

I don't think it is a duplicate, because DHTML menu load all the menu tree where activemenu use AJAX to load only the needed menu parts. This functionality is very important for particular menus which have a lot of children, such as a products catalog. These kinds of menus cannot be loaded like DHTML does, without a big lost of time on page load.

Tree-load vs AJAX-load are significantly different approaches! The choice is important for different use-cases, like b-prod says.
That makes them quite distinct projects.

A quick link on the project page explaining this difference (and cross-linking) would be a very good idea though.

This main difference is now explained in the project homepage.

Automatically closed -- issue fixed for 2 weeks with no activity.