DHTML Lab: HierMenus CENTRAL: Version 5 Setup - Step 6
V5 Setup Instructions
Step 6 of 6
For every menu tree that you have defined that is not permanently visible (see step 4 for a quick discussion of the top_is_permanent menu parameter), you should create a link in your page. In cross-frames implementations, the links should be placed in the navigation page of your frameset. These links should conform to this syntax (below):
<BODY> . . other HTML . <A HREF="/" onMouseOver="HM_f_PopUp('HM_Menu1',event)" onMouseOut="HM_f_PopDown('HM_Menu1')">Webreference</A> <A HREF="/index2.html" onMouseOver="HM_f_PopUp('HM_Menu2',event)" onMouseOut="HM_f_PopDown('HM_Menu2')">Contents</A> . . other HTML . </BODY>
|Link Syntax Details|
|HREF||Make sure that a valid URL is included as the value of the HREF attribute. All browsers that do not support menus will not display the menu trees, and associated links, and need this link to navigate.|
|The event handlers must be onMouseOver and onMouseOut even if you have set the clickStart and clickKill parameter variables to true (displaying and/or hiding menus with mouse click. see step 2.) The menu script will adapt to the parameters you have set.|
|HM_f_PopUp('HM_Menu1',event)||HM_f_PopUp() takes two arguments:|
|HM_f_PopDown('HM_Menu1')||HM_f_PopDown() takes only one argument, but it must be the same menu identifier as the HM_f_PopUp() first argument. That is, if HM_f_PopUp() has "HM_Menu2_3_2" as its first argument, |
|link display text||The link's display text should, of course, describe the menu tree, but should also make sense to users who will not see the menus. For example, the link text should never read: "Menu 2" or "Mouseover to see Menu." Since an old browser user will click on it to navigate, they must be informed of where they are going.|
Once you have included all your in-page links, the menu navigation system for your site is complete! Painless, wasn't it?
You must follow the same steps for all pages that include the menus. Keep in mind:
The same external files can be used for all pages.
Each page can choose which menu trees are displayed by linking only to the wanted menus. Of course, all menus will be created. Some will simply not be used.
In the same way, each page can choose where in the menu tree hierarchy to start displaying each menu tree, by setting the first arguments of HM_f_PopUp() and HM_f_PopDown() as described above.
In cross-frames implementations, only the main frameset itself and the navigation page needs to be specially setup as per these instructions. The individual content pages that will appear within the main content frame do not require any HM specific alterations.
Produced by Peter Belesis and
Created: April 22, 2003
Revised: August 28, 2003