Intersoft's WebUI navigation pane control,WebNavPane, has several unique features that will be explained below in details:
- CaptionDisplayMode
By default, the CaptionDisplayMode is set to "Text" mode when a new instance is dropped to designer surface. You can also have Text&Images, Images, and UseTemplate for CaptionDisplaymode.
picture1 : Use Text And Images as the Caption Mode
picture2 : Use Text as the Caption Mode
- Client Side Events
WebNavPane exposed numerous client side events that you can consume in order to create rich interaction and extensible web applications. Following is the list of available client side events:
- OnBarClick
- OnBarItemClick
- OnClickUnload
- OnInitialize
- OnPaneResize
- Comprehensive Client Side OOP and API
As member of WebUI.NET Framework family, WebNavPane is extensively taking advantage of the client side framework enabling the same structure of object model between server and client side.
Additionally, WebNavPane provides comprehensive API for you to easily interact and manipulate the objects at client side (runtime). For example, you can easily disable or enable a WebNavBar by calling WebNavPane.Enable(). You can also programmatically get the WebNavBar collection or WebNavBarItems collection, changing the caption, tooltip or image of a WebNavBar or WebNavBarItem, and much more properties you can get to work at client side. For a list of complete WebNavPane API, please see "Client Side Reference >> WebNavPane".
- IFrame ContentMode
By default, the WebNavBar will operate in "UseInlineContent" mode when a new instance is dropped to designer surface. UseInlineContent is the most suitable when the contents inside each WebNavBar page are relatively small. UseInlineContent mode utilized .NET Framework's template architecture and therefore all contents are loaded at once in first load (although the contents in inactive bar are set to hidden).
In most cases where you want to develop a more reusable form, you should use UseIFrame as the content mode. When using IFrame mode, you would need to specify the ContentURL which page you want to load for the designated WebNavBar.
The ContentURL accepts three formats of URL:
1. .NET specific application relative URL. This format starts with "~" character, for instance, "~/FolderA/Page1.aspx".
2. Absolute URL. This format starts with "/" character, for instance, "/SharedModule/Page1.aspx".
3. Relative URL. This format usually starts with "." character or no special characters (which assume the page can be found in the current folder's context).
![]() |
You can configure different ContentMode for each NavBar. To apply all NavBar to use a specific ContentMode, configure the ContentMode in WebNavPane control level and leave WebNav's ContentMode to Default. |
- Fully customizable styles and appearances
WebNavPane allows you to customize most of the elements' styles by using strongly typed WebStyle and DynamicStyle properties listed in following:
- FrameStyle
- GripStyle
- NavType
Currently the NavType in WebNavPane is using Outlook2003 Style, later on NavType is also planned to support WinXP Style and many other today's popular styles.
- WebNavPane Designer
Instead of changing properties in Visual Studio Property Window, you can configure most properties shown in "logical group" from WebNavPane Designer. You can also easily manipulate the styles, properties as well as managing the WebNavBar and WebNavBarItems.
![]() |
Most Intersoft's components that exposed rich functionalities, complex objects and collection would implement Component Designer similar to the screenshot above. The consistency of the user interface and functions throughout all Intersoft's components would significantly reduce learning time as well as increasing productivity. |
Related Topics
{Overview}
{Understanding Concepts}


