Features

Professional Look-n-feel

Entirely customizable look-n-feel A lot of pre-designed disable button javascript samples Hundreds of visual effects Custom CSS styles can be applied for all menu settings

Seamless Integration

Cross-frame support - menus work on frameset-based pages Visible over flash, select boxes, iframes, java applets Multiple menus on the same page Amicable to other scripts and css styles Any HTML code can be used inside menu items

Javascript Source Code Movable Menu Disable Button Javascript

High Performance

AJAX menu loading - loads web menu data from the server "on-the-fly". Commonly loads quicker than other html page elements UL/LI items structure Runs well with an unlimited number of submenus and items

Compatibility

Full cross-browser compatibility including IE, Netscape, Mozilla, Opera, Firefox, Konqueror and Safari on Windows, Mac OS and Linux Menu can be populated from a database using ASP, PHP, etc. Search engine friendly Support for any doctypes Fits for secure sites Section 508 compliant

Unrivalled Features

Scrollable, dragable, floating, right-click menus Keyboard navigation - press Ctrl+F2 to enter the menu Unique Java Script API for altering menu "on-the-fly", without page reloading AJAX technology - loads menu data from the server "on-fly and on-demand". Search feature - add the search area in the menu and type symbols. The found words will be higlighted. Sound support!

2.0 Buttons by Web-Buttons.com v3.0.0

Recent Questions

Q: I'm trying to evaluate the possiblity of using your menu in our product. Can we specify our own onclick event handler for the menu item?


A: You're able to use Javascript for each item, for example:

  var menuitems = [
["item text", "javascript:your_code_here"]
];

Unfortunately, you can't assign onmouseover/onClick event to each item.
However, you can achieve this by using standard html objects within items, for example:

  var menuitems = [
["<div onClick='your_code_here'>item text</div>", "index.html"]
];

Q: We are registered users of the Deluxe Menu software. Today I tried to use the Javascript API, but there is something I do not understand and want to ask for support.

First, I set up a very simple menu:

  var menuItems=[
['Menu 1'],
['|Submenu 1'],
['Menu 2'],
['|Submenu 2'],
];

This menu is built via dm_init().

Then, I inspect the menu (in Firebug):

>>> dm_ext_getSubmenuParams(0, 0)
["dm0m0", 2, "", 0, 1]
>>> dm_ext_getSubmenuParams(0, 1)
["dm0m1", 1, "dm0m0i0", 1, 0]
>>> dm_ext_getSubmenuParams(0, 2)
["dm0m2", 1, "dm0m0i1", 1, 0]

Ok, there are three submenus. Now I am going to delete one of them:

>>> dm_ext_deleteItem(0, 0, 1)

"Menu 2" disappears on the screen, this works as expected. But now when I re-inspect the menu using the API, I find that the API reports exactly the same as before:

>>> dm_ext_getSubmenuParams(0, 0)
["dm0m0", 2, "", 0, 1]
>>> dm_ext_getSubmenuParams(0, 1)
["dm0m1", 1, "dm0m0i0", 1, 0]
>>> dm_ext_getSubmenuParams(0, 2)
["dm0m2", 1, "dm0m0i1", 1, 0]

So, it seems the report function continues to know about the original menu structure and reflects it. Am I using the API in a wrong way?

The problem I want to solve is to remove the entire menu dinamico dhtml, in order to rebuild it dynamically. Because I did not see a function aimed to this functionality, my plan was to delete all main menu entries subsequently until the main menu inspector no longer reports an entry. Is there (a better) way to achieve this?

A: Unfortunately, dm_ext_deleteItem() only change visibility of theseitems.

It doesn't delete them completely.

We'll try to fix it in the next versions of Deluxe Menu.

Q: The menu is very large and I am concerned about load speed.

Does the ajax like technology just load the top tabs and then only the sub menus if they are clicked? I have clicked true and added 5 as there are 5 submenus but it does not seem to make any difference.

What can I do to speed up the javascript onclick menu?

A: Check that you've set the following parameter:

  var dm_writeAll=0;

Q: I have been mostly creating my menus by starting with a template file that has the features I need, and then modifying that file by hand (as opposed to using the Tuner program). In this case I am using data-vista-01.js.

When I load my html file that has references to the necessary resources (e.g. .js, gif, etc) in a directory that has the Images folder and Menu folder copied directly from the installed Deluxe Menu program directories, I get what I want.

This is perfect. But I think to myself, surely I don't need all the .js files from the Menu directory, nor do I need all the .gif files from the Images directory, so I started deleting those files one at a time, until I got to the point where Images contained only the Vista1 folder + the empty.gif file, and the Menu folder contained only dmenu.js. My menu now not working.

I'm guessing that some graphic files need to draw the top-level menu bar are missing. But which ones?
So my question is, what files do I really need? Is this something the documentation describes, and if so where?

I hope I don't have to include the full contents of the Menu and Images folder, as they are quite large.


A: Unfortunately, you should add all need images manually.
We'll try to correct it soon.
You can open your data.js file and see what images you're using in themenu and copy tese images into your folder.

You should also change the following parameter:

  var pathPrefix_img="";

There is no need to use all engine files for the menu.
Description of files you can find here:
http://deluxe-menu.com/description-of-files-info.html