Mootools Ipone Context Menu Ul Li by Deluxe-Menu.com
Mootools Ipone Context Menu Ul Li

Menu Screenshots

Mootools Ipone Context Menu Ul Li Dhtml Menue Maker

Features

Cost Effective
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
Cross Frame Javascript Menu Example Mootools Ipone Context Menu Ul Li
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!
Professional Look-n-feel
  • Entirely customizable look-n-feel
  • A lot of pre-designed mootools ipone context menu ul li samples
  • Hundreds of visual effects
  • Custom CSS styles can be applied for all menu settings
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



2.0 Buttons by Web-Buttons.com v3.0.0

Javascript Menu. DHTML Menu.

  • Good menu is an essential part of website commercial success. If people can't find their way around the site, they will fast give up seeking and retire, never to return. So, it's extreme serious that your website has a accurate, precise, prompt, and navigation of immaculate appearance.
    Don't let your web site guests to get lost. Try Deluxe Menu!

Recent Questions

Q: Is it possible set a menu item to pressed when a page is loaded when you have multiple drop down menus on the page?  

I have 2 menus side by side and I was able to set the pressed item with the JavaScript API as described in your FAQs but when I try to show an item as pressed  in a second menu on the same page, the corresponding item in the first menu shows as pressed. Is there a different function that I can use for this or a way to reset the menu ID in the second menu to start from where the first menu left off so I can use the same function?

A: See the first parameter in
dm_ext_setPressedItem (menuInd, submenuInd, itemInd, recursion)
function is index of the menu.

So, if you use several menus on the one page you should use differentmenuInd parameter.

For example you have:

<script type="text/javascript" src="menu/data1.js"></script> //menuInd=0
...
<script type="text/javascript" src="menu/data2.js"></script> //menuInd=1
...
<script type="text/javascript" src="menu/data3.js"></script> //menuInd=2
...
<script type="text/javascript" src="menu/data4.js"></script> //menuInd=3

So, for the second menu you should write:

dm_ext_setPressedItem (1, 2, 5)



Q: Now on IE for Windows, the menus disappear as I roll over them, though not always.
I'd say 90% of the time they fade away as my cursor crosses them.
10% they stay and I can get a good click.

On Safari, they work great.


A: See menu parameters they contain:
  var smShowPause=0;
  var smHidePause=0;

You should set, for example:
  var smShowPause=200;
  var smHidePause=1000;

Try that.


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: Your product is great. I do have one question for you however.

Right now the dropdown (subitem) menus appear based on the smShowPause variable, and disappear based on the smHidePause variable. It is sometimes awkward for users to mouse off the subitem menu that has dropped down, only to have it still hanging there. Reducing the smHidePause variable is not an option because then the menu often disappears before a user has selected a menu option.

The ideal solution is the have the subitem menu recognize when the user has moused off the menu, and then disappear. Is this possible?
if not, I definitely suggest incorporating it into your next build!


A: Try to set these parameters:

  var transition=0;
  var transOptions="";
  var transDuration=0;
  var transDuration2=0;

  var smShowPause=200;
  var smHidePause=200;