Regarding the Mambo drop-down menu, it uses the JSCook javascript routines for admin and the code was recently moved to allow its use in both the frontend and backend. A lot of new templates are appearing on the scene with the JSCook drop-down menus. It's also possible to create tab-like menus using the same library.

For this menu to work in XOOPS, a navigation concept similar to that used in Mambo needs to exist where the menu is dynamically created based on the categories and subcategories defined for the menu items. Rather than treating menus as blocks, the concept of a navigation system needs to be integrated into the core, allowing the menu to be generated in the same fashion as a site map. The easy way out of this is blend the concept of a navigation system into something like wfsection.

The major problem with this menu, especially in admin, is the growth of the menu as more and more items are added dynamically. It eventually reaches the point where the bottom of the menu slides below the bottom of the screen on low resolution monitors. There upcoming solution for this is to modify the Javascript to behave in a manner similar to the EI6 Favorites menu where an arrow appears at the bottom of the menu when it approaches the bottom of the screen. To handle this, they have to pull the users monitor resolution from the HTTP data to compute menu size limits for different monitor resolutions. Some mind boggling show/hide layer routines need to be developed to pull this off.

Does anyone have an active project underway for building a module based on Aidan Peiser's (phpsolutions.co.uk) phProfession 2.6 standalone version?

This is a job bank with a resume uploading feature.

Such a module would require the creation of several user groups to handle module administration and recruiter login. Does anyone know if there is an API for creating groups on-the-fly during module installation?