|
Tigra Menu PRO is a flexible JavaScript DHTML menu solution for commercial applications offering high reliability and wide browsers support. Tigra Menu PRO is neither Microsoft Windows application nor Rapid Application Development System.
No. Tigra Menu PRO is not visual menu building tool. It is menu script itself.
On official site of Tigra Menu PRO script go to the section "Registration and Download". Full latest version of the product within simple demo site will be sent to your e-mail just after secure online ordering process.
Sure, there is whole gallery of demos at official site of the script. Note that demos working with the instance of the script offered. With Tigra Menu PRO you have all features demonstrated in any combinations possible.
Documentation for the latest version of Tigra Menu PRO is available at http://www.softcomplex.com/products/tigra_menu_pro/documentation/
Menu script is downloaded to the browser's cache after first access, so it doesn't consume time on every page download, but it requires to initialize each time anyway.
If the product is internet/intranet web application the licensing is $29 for use within single domain boundaries. All consequent licenses purchased by the same company are $14.5. If product is kind of mass offline application (i.e. presentation on CD) we need to discuss the licensing for particular case.
Pages of single application resides under same domain and share single copy of menu file (menu.js) referred with relative path. So if You could setup all of your sites to share one copy of menu.js not to having domain names here:
<script language="JavaScript" src="menu.js"></script>
they are all single application and require only one license. Otherwise You should purchase licenses for all applications. Each license gives you right for free support and free updates of product (including major versions). Please, read our Terms and Conditions section for detailed explanations.
Just store it. It is like electronic certificate - the proof of your order.
The problems with levels 3 and deep are probably caused by not defined geometry neither for level nor item. Each level of menu is configured independently in menu geometry structure (usually MENU_POS variable in menu_tpl.js file). Parameters assigned array value. Each element of array corresponds menu level with the same index. More levels expected - more elements required for each parameter.
To set menu position you need to modify menu_tpl.js file. In Tigra Menu PRO documentation there is remark for parameters:
// E. Horizontal Offset between adjacent levels* in pixels MENU_POS['block_left'] = [5, 0, 120, 140, 160]; // F. Vertical Offset between adjacent levels* in pixels MENU_POS['block_top'] = [50, 26, 10, 10, 10];
* - This parameter for root level (the one with index 0) is menu offset from the document's left upper corner, so use it for menu positioning on the page.
So, in case above menu position on the page is x=5px, y=50px.
To set Tigra Menu to be vertical you need to specify zero horizontal block offsets (block_left parameter) and vertical offset equal to item height (block_top parameter). The difference between vertical and horizontal menu look is only in those offsets.
This is caused by items overlapping. Next item in the same block is positioned too close (as for single line items) and wrapped line is overlapped by next item. Last items can't be overlapped since there are no items after them so they look ok in any case. Modify height of the wrapping item and vertical offset of the next item to allow some space for wrapped lines
Alignment feature is available from v2.0 of Tigra Menu PRO. You need to specify align parameter in menu geometry configuration file.
// Menu alignment - (left, center, right) MENU_POS['align'] = 'center';
Menu item definition is just an array. If this array has 1 to 3 elements then item has no sub-items, every next element should be sub-item defined the same way as parent item - in array like style.
There is an error in your MENU_ITEMS structure that usually resides in file menu_items.js. Demo menu configuration in the package you receive after ordering process initially has no errors in this structure. Make little modifications and verify results each time to detect easily when error appears.
Most frequently made errors in MENU_ITEMS structure are:
Tigra Menu PRO supports frames targeting since ver.1.1.
To open document in new window specify word '_blank' as name of the target frame for the item. Target frame is specified in menu tree structure: Replace second field of menu item definition (link section) with three element array to allow additional link related parameters. Those elements are:
0 - link itself. This text will be inserted into href attribute of item's anchor tag.
1 - target name. This text will be inserted into target attribute of item's anchor tag.
2 - tooltip. This text will be displayed in small box appearing over the item after mouse pointer moved to it. Use it to additionally describe the item.
You can control document in one frame and update all dependent frames with the javascript function called as onload handler for that document. You can also call javascript function just when item is clicked.
You can use inner html for that. Specify item color directly in item's caption using html tags. Writing wrapper for this case will simplify maintenance.
Make sure you don't apply conflicting settings with both inner html and styles. For example: if you have inner html formatting (direct or with wrapper) having border, make sure you haven't defined border with CSS styles.
You have two ways to do that:
You should check if pixel.gif image is available online at the same path that is specified in menu geometry structure (usually menu_tpl.js file) parameter 'pixel_path'. Basically you should upload ALL menu related files to server exactly as they were on your local computer.
I'm pretty sure this is impossible. Unfortunately you will not find any menu solution that will function this way. The only thing that is possible (but not yet implemented in Tigra Menu) is tuning some fixed number of menu levels to fit in one frame and making other levels to show in other frame (no item can overlap frame border)
There is no need to support dynamic styles in PRO version since there is more flexible way to achieve the same results: you can define styles for any state separately. You can even have different captions and item formatting for different states.
Just link different menu_items.js files to different pages. Each local menu tree should have current item highlighted. It is also possible to write the wrapper comparing current URL with the link and highlighting items accordingly. Another way is to generate menu tree dynamically with the server side script (menu_items.asp or menu_items.cgi) that receives section name or id and modifies coloring parameters for items accordingly.
Unfortunately, this is common problem with windowed controls (html listboxes, flash movies) and absolutely positioned html elements (all types of cross browser javascript menu systems). There is no known solution for this issue. The only suggestion is to avoid overlapping in your site design.
Any html allowed within menu items so you are free to use something like
<div style="width: 100%; text-align: center;">your caption</div>
If same alignment is required for many items you may write simple wrapper.
As most of JavaScript Menu systems Tigra Menu PRO is positioned absolutely in some of the higher layers over the html document, so it is not placed inside some relatively positioned element. With Tigra Menu PRO you can achieve the same result setting menu position right over the element of your choice even if it is right or center aligned. Please, don't put menu initialization block within relatively positioned elements as it prevents menu from working with some browsers correctly.
I guess your mistake is that you've copied both structure declaration and structure definition and then modified only structure definition:
i.e. if you copy:
menu_items.js to menu_items1.js and menu_tpl.js to menu_tpl1.js
Make sure you have changed ALL references to MENU_ITEMS in files to MENU_ITEMS1 and MENU_POS to MENU_POS1 accordingly. Again, you should change all corresponding instances in those files.
BTW: Don't forget about CSS class naming convention for menu instances when defining classes for second menu.
Check class names for second menu in its CSS page. ALL class names should start with .m1 for second menu
You don't need another menu.js file, but you should create all other configuration files that should be different for other menus. I think that the easiest way for you to learn how to add more menus to page is to see demo (included in the distribution package).
Put menu initialization block (the one with new statement) just before closing body tag.
Tigra Menu PRO coded to achieve same results in all browsers in its compatibility list, however when you use style settings we can't guarantee the same look because different browsers have different level of CSS support and sometimes even render the same css rules in different ways. We recommend using wrappers to achieve best browsers compatibility.