|
Feature |
EO.Web Menu |
ASP.NET 2.0 Menu |
| Inline CSS Style |
EO.Web Menu supports CSS class and inline CSS text. You can modify inline
CSS style in Menu Builder and preview the result without running
the page. Save tremendous development time.
|
No support for inline CSS text.
Only supports CSS class. Requires users to switch back and forth between
.css file and .aspx file and run the page to work out the
desired visual appearance.
|
| Design Time Preview |
EO.Web Menu Builder can preview the Menu without leaving Menu
Builder. This means that you do not have to confirm and save your changes
and then run the page to see the result.
|
No support.
You must run the page to see the result.
|
| Type Editors |
EO.Web Menu provides a variety of intuitive and powerful type editors,
such as Image Url editor, built-in Image Browser, Inline Style Editor,
Expand Direction Editor, etc, to edit menu and menu
item properties.
|
Very basic support.
Mostly text box/combo box, or using the built-in Image Url
picker.
|
| Look Items |
EO.Web Menu supports look items. Look items are special navigation items from which
other navigation item inherits style settings. You can assign look item to navigation item
on navigation item level, on the navigation item group level or inherits from skin.
|
Only supports "Level Styles".
You can only assign style templates based on the level of the navigation item.
|
| Theme & Skin |
EO.Web Menu fully supports theme and skin. You can save
any EO.Web Menu as skin so that other menus can inherit the
skin Menu's properties, Look items and navigation item properties based on
the hierarchy from the skin menu. Target menu will look the same
as the skin menu.
|
No special support on skin except for the standard ASP.NET 2.0 theme
support.
The standard theme support does not work well on a component with
hierarchical structure like menu.
|
| Built-In Skins |
EO.Web Menu includes built-in professional- looking MSDN,
Office XP/Office 2003 style menu skins.
|
Only supports a few very plain "Auto Format" templates.
|
| navigation item States |
EO.Web Menu supports 5 different states on each navigation item: Normal, Hover,
Down, Selected & Disabled. The menu automatically switches styles and
images associated with these states when user navigates through the
menu.
|
Less supported states.
Only supports 3 states: Normal, Hover & Selected states. No separate
image is associated with each state.
|
| Icons & Images |
EO.Web Menu supports left icon and right icon. You can specify different
images for different states, for example, a image for normal and another
image for hover state.
|
Only supports left icon and pop out image. You can not specify different images
for different states.
|
| Image-Only Menu |
Fully supported. You can specify different images for different states.
|
No support.
|
| Built-In Check/Uncheck support |
EO.Web Menu supports CheckIconUrl property which allows you to place a
check/uncheck icon to the left of the menu item with a single
line of code either on the server side or on the client side.
|
No support.
|
| Effects |
EO.Web Menu supports 60+ DHTML expanding and collapsing effects
& transitions. User can specify effect types, duration and
step on each menu group.
|
No effect support.
|
| Cross frame |
EO.Web Menu provides transparent cross- frame support without the
need of writing a single line of code.
|
No cross frame support.
|
| Client side JavaScript interface |
EO.Web Menu provides complete client side JavaScript object modal and
interface. User can modify the menu on the fly at client side without posting
back to the server. A rich set of client side events is also
provided.
|
No client side JavaScript interface.
|
| Slide Menu |
As an additional separate control, Slide Menu provides Windows
XP/Outlook-like style sliding pane. It inherits almost all EO.Web Menu
functionalities, including cross frame support.
|
No such functionalities.
|
| Scrolling |
EO.Web Menu, Slide Menu and TabStrip support automatic and forced scrolling. |
No such functionalities. |
| Nesting ASP.NET Controls |
Can nest any other ASP.NET control through data binding or directly. Each
navigation item can have its own child controls independently.
|
Partial supported through data binding. Cannot nest ASP.NET control
directly. All navigation items must have the same set of children controls.
|