Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
I have created a module for use on my own projects that I believe would be useful to others in the community, so I would like to share it as part of the contrib repository.
My module creates a theme-able, unobtrusive, collapsible floating menu for content editors and managers. There are several excellent modules providing administrator menus (most notably admin_menu) , but we have had trouble adapting those for use by non-administrative users on large scale sites.
This module features:
- the ability to select any existing menu from within your Drupal installation
- simple CSS themability, with three themes included
- jQuery UI draggable floating "window" that doesn't require inclusion in a certain region of a theme (window is collapsible to save space and maintains persistent positioning through page loads)
- seamlessly compatible with dhtml_menu for an even smoother experience
Beyond just wanting to share this module, I would like to be able to get more eyes on it to suggest improvements and further development potential.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | floating_manager_menu-fa523d58449c.gz | 9.06 KB | jdschroeder |
| #5 | floating_manager_menu-v0.1.1.tar_.gz | 9.01 KB | jdschroeder |
| #3 | floating_manager_menu.tar_.gz | 9.15 KB | jdschroeder |
| #1 | floating_manager_menu.tar_.gz | 14.56 KB | jdschroeder |
Comments
Comment #1
jdschroeder commentedComment #2
avpadernoComment #3
jdschroeder commentedUploading a minor update.
- removes LICENSE.txt
- adds a z-index property in the themes to prevent the menu from being hidden by other positioned elements
Comment #4
matt2000 commentedHave you discussed packaging this with DHTML menu module with it's maintainers?
I think HTML inside of a t() function is discouraged -- see floating_manager_menu_settings() line 181.
Could you use system_settings_form() to save you the trouble of floating_manager_menu_settings_form_submit() ?
floating_manager_menu_theme_list() sounds dangerously prone to namespace collision. naming your menu skinning system 'themes' might not be a good idea in the first place....?
You shouldn't list menu as a dependency, since it is required.
Comment #5
jdschroeder commentedPersonally, I'm not convinced that the modules are really that closely related that they warrant that; however, on your suggestion, I have contacted the developer of that module to seek his opinion.
Of course. I've fixed this.
I could, and I now have.
This is something that had crossed my mind, and I have now changed the terminology to skins rather than themes.
I've removed that dependency.
Updated code attached.
Comment #6
matt2000 commentedCool. I like it.
One trivial note: you still use the term 'theme' in the constant FLOATING_MANAGER_MENU_THEME .
But no reason to delay CVS access on that point.
Comment #7
jdschroeder commentedThanks Matt. Not sure how I missed that constant, but I've got it fixed now, too.
Comment #8
avpadernoComment #11
avpaderno