Contents / User Interface Reference / Menu options / Output

Output is where you specify where the output web page containing the menu and the menu files (images, scripts) should be generated. This section also contains JavaScript-related options and options which enable insertion of multiple menus into a single web page.

Output / Upload output to an FTP server
Selecting this option will result in uploading output files to an FTP server.

Output / Upload output to an FTP server / Remember password
Select this option if you want DHTML Menu Studio to store your login and password. Please note that storing your FTP password is insecure!

Output / Upload output to an FTP server / Remember password / Password
Your password for the FTP connection.

Output / Upload output to an FTP server / Use proxy server (firewall)
Select this option if you are behind a firewall and cannot connect directly to the FTP server (click the 'Proxy settings' button to specify detailed options)

Output / Upload output to an FTP server / Server address
Specify the address of an FTP server, e.g: ftp.xtreeme.com. Do not include the ftp:// protocol prefix

Output / Upload output to an FTP server / Login
Your login name for the FTP connection.

Output / Upload output to an FTP server / Port
Port for the FTP connection. Usually the default value of 21 will be correct.

Output / Upload output to an FTP server / Use passive mode
In passive mode, it's the client that establishes the connection (like a web browser). This may be necessary with some firewalls which don't allow connections from the outside.

Output / Physical location of generated (output) files
Options in this category are used to set the physical location of files generated by the program. This is either a local/network location (e.g. c:\dir\... or \\server\dir\...) or an FTP location (if using the FTP upload option -- e.g. /home/abc/www/...)

Output / Physical location of generated (output) files / Output page location same as template file used
This option will automatically set the location of the output page according to the imported template file. Using this option will result in the original template file being replaced by a similar page but with output code inserted by the program. You cannot use this option if not using a template file.

Output / Physical location of generated (output) files / Output file name
Specify the name of the output HTML file (default: menu.html). Please specify file name only without a path.

Output / Physical location of generated (output) files / Output directory for HTML files
Specify the directory where output menu files (HTML documents) will be saved. This should be a local directory (e.g. c:\menu\...) or, when uploading to an FTP server, a relative or absolute FTP directory (e.g. /usr/name/www/menu)

Output / Physical location of generated (output) files / Output directory for menu files (images and scripts)
This is a local directory (on an FTP directory if uploading to an FTP server) where scripts and images generated by the program will be saved. This directory should reflect the path specified in the field 'Menu files directory'. You can leave this option empty to generate scripts and images in the same directory as output HTML files. See Q3029 in the FAQ on our website for more help.

Output / HTTP paths used in output HTML code
Options in this category are used to set paths used on HTML pages to access files (images, scripts etc.) generated by the program. These must be relative or absolute paths, just like URLs specified in the <a href=xxx> tag, e.g. http://server/dir/ or /dir/ or ../dir

Output / HTTP paths used in output HTML code / Menu files directory (relative or absolute HTTP path)
Specifies the HTTP path to the directory containing scripts and images generated by the program. This can be an absolute path (e.g. '/menu' or 'http://www.mydomain.com/menu'), relative path (e.g. 'menu'), or you can leave this field empty if 'Output directory for menu files' is left empty as well. The value of this field should be the HTTP representation of the directory specified in the field 'Output directory for menu files'. See Q3029 in the FAQ on our website for more help.

Output / Multiple menus
Select this option if you want to embed two or more menus on a single HTML page.

Output / Multiple menus / Menu ID
Please leave this option unchanged unless creating multiple menus on a single web page. Menu ID is the index of the menu on a web page. The first menu should have ID = 1, the second menu = 2, and so on...

Output / Multiple menus / Optimize size of generated JavaScript files
Select this option if you want to minimize the size of the generated JavaScript files. Warning! If you're going to use one JavaScript file for different (feature-wise) outputs (e.g. two menus on a single page or different dynamic trees embedded into multiple pages) you should unselect this option because certain features of the script (e.g. fading effect for menus) may be unavailable in the optimized version.

Output / Output format
Specifies how DHTML Menu Studio should output the HTML code. This can be one of the following values.

Output / Create a separate file for JavaScript code
Select this option if you want all menu-specific JavaScript code to be generated in an external .js file. The advantage of this solution is that the external .js file will be cached on end user's computer and therefore all the pages containing the menu will load faster.

Output / Dynamic creation of menu structure
This option allows you to build the menus using server-side scripts based on e.g. currently logged-in user's permission or based on data dynamically pulled from a database. You can specify if you want the program to create output code in form of PHP, ASP, or simply JavaScript code.Please note that if you're using a bitmap scheme and the top-level menu bar items are created as images, you will only be able to dynamically add popup items (top-level items will be fixed).

Output / Output search-engine friendly code
Selecting this option will make the output HTML code search engine friendly by outputing <A> tags (HTML links) for each menu item inside a <noscript> tag, therefore allowing search spiders to crawl through your site.