|
While the Portal Object provides all the common operations such as opening up a level and menu, you need to specify the the action to carry out when the item is clicked. The actions are presented as JavaScript callback functions. They include:
| Callback |
Arguments and Description |
| LevelOn |
(level)
Called when a Level is opened |
| LevelOff |
(level)
Called when a Level is closed |
| MenuOn |
(topic, level, page, param, parent)
Called when a Menu is opened |
| MenuOff |
(topic, level, page, param, parent)
Called when a Menu is closed |
| ItemOn |
(topic, level, page, param, parent)
Called when an Item is opened |
| ItemOff |
(topic, level, page, param, parent)
Called when an Item is closed |
| ItemAction |
(topic, level, page, param, parent)
Called when an Item is clicked |
|
|
When an item (i.e. topic) on the menu is clicked on, the doMenuItem client script (provided by the BEE Portal) will be called. This script assumes the menu is opened in a hierarchical form so only the ancestors of the active item or the ancestors' siblings will be opened and therefore be clicked on.
So all it needs is to close all the submenus below the newly clicked item, before such item is opened.
This calling sequence will occur:
- Close the active item currently opened: ItemOff()
- Close the active menu: MenuOff()
- Close the level: LevelOff()
- Go up one level
- Close the active item at the level: ItemOff()
- Repeat from step 2 until completing the level of the newly clicked
- Open the newly clicked item to make it active: ItemOn()
- If the item is a menu, open the next level (LevelOn()) and open the menu at that level (MenuOn())
- Call ItemAction()
However, the assumption that only ancestors or their sublings will be clicked on may not be true if you allow inter-page linking. In that case, another client script (also provided by the BEE Portal) doDirectItem will be called. It basically called doMenuItem from the root menu item all the way down to the item wanted. |