Features

Easy Setup

De Luxe Tuner. GUI interface to create your submenus con contenido ajax menus easily and in no time Sensible menu parameters for manual editing

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

Mouse Over Menu Drop Down Submenus Con Contenido Ajax

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

Professional Look-n-feel

Entirely customizable look-n-feel A lot of pre-designed submenus con contenido ajax 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

Recent Questions

Q: How do you labeling the various segments of your page to utilize the horizontal menu tabs?


A: See, for each item you should assign the ID property of the contentDIV (see data file with your menu parameters).

["Style Name","contentName", "", "", "", "", "1", "", "", ],
["-","", "", "", "", "", "0", "", "", ],
["Style Description","contentDescription", "", "", "", "", "", "", "", ],
["-","", "", "", "", "", "0", "", "", ],
["Style Variations","contentVariations", "", "", "", "", "", "", "", ],
["-","", "", "", "", "", "0", "", "", ],
["Empty","", "", "", "", "", "2", "", "", ],

And on your html page you should create DIV's with such ID.

<div id="contentName" style="height: 0%; visibility: hidden;" class="tabPage">
<br><br><br>
<p align=center><img src="img/style01_title.gif" width=140 height=90 alt="Glass Style Tabs"></p>


<br><br><br>

You should paste your content here!!!!!
</div>

<div id="contentDescription" style="height: 0%; visibility: hidden;" class="tabPage">
<br><br><br>
<p align=center><img src="img/style01_title.gif" width=140 height=90 alt="Glass Style Tabs"></p>

<br><br><br>

You should paste your description here!!!!!
</div>

You can paste any code within DIV's (PHP, Javascript ...)

Q: We are using your deluxe menu on our live site, but I have a question about the initial setup of the menu.

I need to update the site and a create a new version where the Deluxe Menu is painted, but not initially displayed until the user has been validated. We are runing the entire site from a single page with multiple iFrames. I have been using the code document.getElementById('dm0m0').style.visibility = "hidden"; to hide the menu during startup, but I would rather have the floating menu hidden initially and then displayed as the user is validated and gain access to the functionality.

So the question is: Is there a property in the data.js file - or any other file - where the menu can be hidden initially until needed?

A: You can hide the menu onloaddocument.getElementById('dm0m0').style.visibility = "hidden";

And then show the floating menu when your user will be validated.

Q: Does this cross browser menu support only english menus or I can make an english and russian menus as well with deluxe menu multiple license?

A: Actually you can use any language in the cross browser menu.

Check that you've set "Tools/Use utf8 encode" in Deluxe Tuner.

Q: I'm testing the trial version and I'm having a little problem with the state saving. Everytime it navigates to another page, it does not save the state, even with

  var tsaveState=1;

In fact, it actually opens up a different menu other than the one I originally clicked.


A: See, if you open pages (with menus) from different folder it means that you open different menus. So, when you change a state, for example, of the first menu within "newzap/" folder and then open another page with the menu within "newzap/learn/", browsers looks for another cookie file and can't find it and the second menu stays in a default state.

Try to set different

  var tsavePrefix="menu1";
  var tsavePrefix="menu2";
  var tsavePrefix="menu3";

for different menus.
That should work.