Recent Questions
Q: I want to emulate all browsers with the same transition. When mousing over a dhtml pulldown menu - the submenu should appear with no effect.
A: To turn off transitional effects you should set the following parameters:
var transition=-1;
var transOptions="";
var transDuration=0;
var transDuration2=0;
Q: Do you have a template example of creating menu javascripts using data stored in a database?
A: You may generate a menu from a database or XML using any server-side script, e.g., PHP, ASP, VB, etc.
However, these scripts don't work inside of Javascript .js files,
so, you should move parameters of a menu from a .js file into an html-page, e.g.:
<!-- Deluxe Menu -->
<noscript><a href="http://deluxe-menu.com">Javascript Menu by Deluxe-Menu.com</a></noscript>
<script type="text/javascript"> var dmWorkPath = "menudir/";</script>
<script type="text/javascript" src="menudir/dmenu.js"></script>
<!-- (c) 2006, http://deluxe-menu.com -->
<script type="text/javascript" language="JavaScript1.2">
// and describe parameters of a menu
var parameter1=value1;
var parameter2=value2;
etc.
var menuItems = [
// here you generate items using server-side scripts (php, asp, vb, etc.)
];
</script>
The example of the menu working with PHP/MYSQL you can find here:
http://deluxe-menu.com/rq-loading-bar-MySQL-support.htmlQ: I am very interested in using your deluxe menu products for my new website design, particularly the Tree Menu. I've been looking at the javascript tree source and am a bit worried that the links used will not be recognised by Search Engine robots - do you have any information regarding implementation of your menus so that the links are fully visible to search engines ?
A: You can generate search engine friendly code.
Deluxe Tree is a search engine friendly menu since v2.4.
To create a search engine friendly menu you should add additional html code within your html page:
<div id="dmlinks">
<a href="http://deluxe-menu.com">menu_item_text1</a>
<a href="http://deluxe-tree.com">menu_item_text2</a>
...etc.
</div>
To generate such a code use Deluxe Tuner application.
You can find this GUI in the trial package.
Run Tuner, load your menu and click Tools/Generate SE-friendly Code (F3).
Q: There is "Incorrect Copyright" message on our website in IE7. Please, help!
A: Now on your website you're using Deluxe Menu v1.14.
You see "Incorrect Copyright" message because you're using old version of Deluxe Menu. We've fixed this bug in the new version - v2.0.
How to upgrade to v2.00
---------------------------------------------------------------
You can download the licensed engine .js files from the same link in your license message.
Deluxe Menu v2.00 has new parameters and features.
To upgrade to v2.00 you should do the following.
Step 1.
1.1 For Windows users
a. Run Deluxe Tuner v2.0
(can be found in the trial menu package v2.0
http://deluxe-menu.com/deluxe-menu.zip).
b. Open menu data file (.js file where menu parameters are placed):
select File/Open…
c. Save the file: select File/Save, then click "No" button when the dialog box appears.
1.2 For other OS users
a. Open menu data file (.js file where menu parameters are placed) in a text editor.
b. Make sure that the following variables exist in the data file:
var keystrokes = 0;
var dm_focus = 1;
var dm_actKey = 113;
var dynamic = 0;
var smHideOnClick = 1;
var itemAlignTop = 'left';
var smSmartScroll = 1;
var dmAJAX = 0;
var dmAJAXCount = 30;
var dmRTL = 0;
var dmObjectsCheck = 0;
var menuBackRepeat = "repeat";
var menuHeight = "";
var transDuration2 = 200;
If one of the variables doesn't exist - add it at the beginning of the file.
c. Save the file.
Step 2. Now open HTML-page that contains Deluxe Menu.
Step 3. Replace existent <noscript></noscript> tags of the menu by the following code:
<noscript><a href="http://deluxe-menu.com">Javascript Menu by Deluxe-Menu.com</a></noscript>
Step 4. Save HTML-page.
Step 5. New engine v2.00 has 7 .js files.
They are:
- dmenu.js
- dmenu4.js
- dmenu_add.js
- dmenu_dyn.js
- dmenu_key.js
- dmenu_cf.js (new v2.00)
- dmenu_popup.js (new v2.00)
Replace all old .js files by the files from v2.00.
Try that.