 UltimateMenu Release History |
UltimateMenu 3.3 - 11/03/2008 |
Side-by-side Installation: Install ASP.NET 1.1, 2.0, and 3.5 editions side-by-side on the same machine, and work with all of them in parallel.
|
 |
UltimateMenu 3.2 - 01/08/2007 |
AJAX Enabled: Supports UltimateAjax and ASP.NET AJAX.
|
|
UltimateMenu 3.1 - 08/02/2005 |
XHTML Support: Fully compliant with XHTML Transitional. VS.NET 2005 ready.
|
Overlay in HTTPS: Menu overlay feature is now supported in HTTPS pages.
|
Multiple Sources for Context Menu: Context menu can be associated with multiple controls in a comma-delimited form.
|
New Default Settings: Introduced new default width settings for menu items, submenu items, and right icons to build new menus from scratch easily.
|
New Style Settings: Updated the default CSS class definitions to design professional looking menus with no effort.
|
New Method To Change Item Attributes: Introduced SetItemAttribute to modify item attributes programmatically.
|
Renewed Samples: Redesigned most of the samples with the new look-and-feel.
|
|
UltimateMenu 3.0 - 07/04/2005 |
Full Sample Projects: Provides full C# and VB.NET sample applications.
|
|
UltimateMenu 2.3 - 02/12/2005 |
CurrentUser: You can set the CurrentUser property at runtime to the user
who logged into the system to let him see only the menu items he is allowed to
see based on his user permissions set by the AllowedUsers property on each
topmenu or submenu item.
|
CurrentUserSessionVar: You can set the CurrentUserSessionVar property to the session variable that holds the current user logged into the system. Then the menu
control will automatically retrieve the value of that session variable and set it to the
CurrentUser property.
|
AllowedUsers: You can set the AllowedUsers property of any topmenu or
submenu item to a list of users in comma separated form so that only those
users can see this item. If this property is not set for an item it will
displayed by default.
|
|
UltimateMenu 2.2 - 11/14/2004 |
TabView: It is as easy as setting the TabView property to True. The rest
is all about style definitions to create a professional look and feel that will
reflect your company image. Even though you have the HighlighPath property set
to False it tries to match the URL of the page to the URL of the menu items to
initially open one of the topmenu items. Then it will keep the topmenu and its
immediate submenu open to act like a tabview.
|
ShowPath: You can now show the mouse traversal path while you are
passing the mouse over menu items. When you set the ShowPath property to True
it will keep the items on your navigation path in their active form. Note that
this is different than the HighlightPath property that finds the navigation
path based on the URL match of the current page with the menu items.
|
AutoScrollHeight: If you set the AutoScrollHeight property to True it
will automatically adjust the height of the vertical scrolling submenu based on
the height of the browser window. If there is enough space in the browser
window it hides the scroll arrows. Otherwise it opens a scrolling submenu with
the height of the window, and adds scroll arrows to the top and bottom portion
of the submenu.
|
OnMouseOver Functionality: You can use the ItemOverClientCall and
ItemOutClientCall properties to make client-side function calls when the mouse
gets over an item and leaves it, respectively. This will give you the ability
to modify your web page on client-side depending on user actions on the menu
without making trips back to server.
|
|
UltimateMenu 2.1 - 06/11/2004 |
MenuBuilder: MenuBuilder, our visual designer tool, is now fully
integrated into VS.NET. You can right-click on the UltimateMenu server control
on your web form, and select Karamasoft MenuBuilder to open your menu from an
XML file or database directly from inside VS.NET. If you don't use VS.NET you
can still use MenuBuilder as a stand-alone ASP.NET application to design and
build your menus visually. However, this latest improvement will make life much
easier for ASP.NET developers using VS.NET.
|
DataBinding: DataBinding is now easier than ever. If you prefer to keep
your menu in database rather than an XML file you can load your menu from
database by only providing a connection string and a menu id. You don't need to
create a dataset or bind to it anymore. Everything is taken care of behind the
scenes by the UltimateMenu control. However, you can still set the source of
the menu to a dataset if you want to do any customizations such as displaying
different portions of the menu based on the user rights. Sample code is
provided in the Tutorial for both scenarios.
|
Opera: Opera 7.5 and higher versions are now supported.
|
|
UltimateMenu 2.0 - 01/20/2004 |
DataBinding: You can set the source of the menu to a dataset that you
created from a database by using ADO.NET at run-time. All you have to do is to
set the DataSource property to the dataset that you created from a database
such as SQL Server, Access, etc. by using ADO.NET, and call the DataBind()
method of the control.
|
UserRights: Using the DataBinding techniques you can easily display
different sets of menu items per user depending on their privileges by only
making a simple join operation on your menu and user tables. As a matter of
fact you will have the power and flexibility to load your menu from as many
tables as you want based on your implementation needs.
|
ServerControl: You can set the item type to ServerControl if you want to
insert a server control (asp:control) or a combination of server and HTML
controls into the UltimateMenu control on a web form (aspx page).
|
ContextMenuSource: You can attach your context menu to a server or HTML
control by using its ID on your web page, and it will open up when the user
right-clicks on that control.
|
Timeout: You can set timeout values for both the duration to keep the
submenu open when the mouse is not over it (HideMenuTimeout), and the duration
to wait before opening a submenu not to disturb the user while carrying the
mouse over menu items (ShowMenuTimeout).
|
Overlay: You can set the MenuOverlay property to let the submenus open
over IE windowed controls such as select boxes and ActiveX controls. Submenus
will partially cover these controls rather than hiding them altogether.
|
HotKey: You can set a hotkey (shortcut key combination) to a menu item
so that the user can press that combination to activate that item as if it is
clicked by mouse. This keyboard support might also be helpful for disabled
users who can learn the shortcut keys to operate and navigate your website.
|
SubmenuOpenDirection: Even though submenus arrange their locations
automatically you can override this behavior by setting the opening direction
of each submenu. You can set VerticalOpenDirection or HorizontalOpenDirection
depending on the layout of its parent.
|
SubmenuAlign: Vertical submenus are aligned at the top, while horizontal
submenus are aligned at the center of the parent item by default. You can
change this default behavior by setting the alignment of each submenu. You can
set VerticalAlign or HorizontalAlign depending on the layout of its parent.
|
ItemStatus: You can display text at the status line of the browser
window when the mouse is over each menu item.
|
Less HTML: We minimized the HTML code generated by the UltimateMenu
server control with the introduction of a totally new HTML structure along with
the new JavaScript code compared to the old versions.
|
Backward Compatibility Issues:
|
1. Group: Scroll property needs to be changed to Scrolling.
|
2. Item: Image property needs to be changed to ImagePath.
|
3. Item: ImageOver property needs to be changed to ImageOverPath.
|
Also note that Internet Explorer on MAC is not supported with the DHTML
features of UltimateMenu anymore. It will still work with IE on MAC, but it
will be treated as a down-level browser with limited functionality. Even though
this is a step back from the earlier version we had to introduce this
limitation due to a lot of differences in IE on MAC, and the lack of support
from Microsoft on those issues.
|
|
UltimateMenu 1.2 - 02/21/2003 |
Down-Level Browser Support: In addition to its current support
for IE4+, NS6+ and Mozilla 1, now it fully supports IE5+ for MAC, and
supports all downlevel browsers such as NS4x, and Opera with limited
functionality.
|
|
UltimateMenu 1.1 - 12/28/2002 |
New Features: PathFindingMethod, SelectedItemID, BaseURL, and .NET Framework 1.1 Compatibility.
|
|
UltimateMenu 1.0 - 07/01/2002 |
Initial release.
|