Maybe add support for other menu methods besides DHTML Menus?
| Project: | Bookmarks |
| Version: | HEAD |
| Component: | User interface |
| Category: | feature request |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | by design |
| Issue tags: | Suggestion |
Jump to:
I apologize in advance if this idea has already been suggested, but it's extremely early here and I have not yet had my first coffee of the day. ;)
From the project page:
DHTML Menus 6.x-3.2+ are now required. If there is enough opposition, I can recreate the wheel within my code but since DHTML Menus already does what I need it to I see no reason to do so.
I am actually in no way whatsoever against DHTML Menus, as it is indeed a fine module and I myself do use and enjoy it, but after having used sun's wysiwyg API it strikes me that something similar would be quite nice for something like this module. If one happens to be using jQuery Menus (for example) instead of DHTML Menus, it would be a very slick thing if this module detected and used that instead of DHTML Menus or perhaps offered the user a choice in some way...
I'm not saying that you should make efforts to support every possible menu out there or anything. Just that it would be nice if perhaps a few of the best and most popular menus were an available option.
It's just a thought I had, and not really in any way a particularly pressing issue I must admit, but it would be a rather impressive little additional feature that would just make this already fine module just that little bit nicer... ;)
Anyhow, that's my suggestion/idea... Thank you very much for such a great little Drupal module. Your hard work creating it is greatly appreciated. :)

#1
Folders will not work properly without some type of expandable menu system. DHTML Menus interfaces with the menu system in a clean manner that requires no additional code from me. Without DHTML menus the folders are always expanded and won't collapse.
At this time, I won't be removing the DHTML Menus requirement. I may review the other menu modules and see if they can provide the same support at which point it would be possible to remove the requirement and just include a disclaimer stating why one of them is needed. Of course, a fix to the menu system itself would also solve this problem.