Asp Menu control

This contol supports many features but of the many features the ones that are of interest to interface designers are the features that supports customization of the menu's appearance through themes, user-defined images, styles, and user-defined templates.

These features are the subject of this post.


The Menu control displays two types of menus: a static menu and a dynamic menu.
For the most part the menu items you see would be defined as the static menu items and the menu items that are viewable only on rollover are defined as the dynamic menu items.

Menu item style property
DynamicHoverStyle
The style settings for a dynamic menu item when the mouse pointer is positioned over it.
DynamicMenuItemStyle
The style settings for an individual dynamic menu item.
DynamicMenuStyle
The style settings for a dynamic menu.
DynamicSelectedStyle
The style settings for the currently selected dynamic menu item.
StaticHoverStyle
The style settings for a static menu item when the mouse pointer is positioned over it.
StaticMenuItemStyle
The style settings for an individual static menu item.
StaticMenuStyle
The style settings for a static menu.
StaticSelectedStyle
The style settings for the currently selected static menu item.


Image property Properties

DynamicBottomSeparatorImageUrl
An optional image displayed at the bottom of a dynamic menu item to separate it from other menu items.
DynamicPopOutImageUrl
An optional image displayed in a dynamic menu item to indicate that it has a submenu.
DynamicTopSeparatorImageUrl
An optional image displayed at the top of a dynamic menu item to separate it from other menu items.
ScrollDownImageUrl
The image displayed at the bottom of a menu item to indicate that the user can scroll down to view additional menu items.
ScrollUpImageUrl
The image displayed at the top of a menu item to indicate that the user can scroll up to view additional menu items.
StaticBottomSeparatorImageUrl
An optional image displayed at the bottom of a static menu item to separate it from other menu items.
StaticPopOutImageUrl
An optional image displayed in a static menu item to indicate that it has a submenu.
StaticTopSeparatorImageUrl
An optional image displayed at the top of a static menu item to separate it from other menu items.

The view above-the-fold is called the viewport

I always wondered what's the technical name for the area of the screen that is above-the-fold of the monitor. Actually I think the expression above-the-fold is jargon taken from the print world. In any case I stumbled across this definition from an online resource webreference.com.

The view above-the-fold is called the viewport. Here is the technical definition:
The canvas is a large flat space on which the document is rendered, and the viewport is the bit in your browser's window where the document appears. If the canvas is bigger than the viewport, only a part of the canvas will be visible at any time, and browser will usually allow you to scroll around the document using a scroll bar or something similar.

How to evaluate information architecture of your intranet sites before migrating them to MOSS.

If you are moving from 2003 to moss the best way to assess the restructuring is to logically categorize the content of sites in your current environment. Here how I did it:

Create a list in excel with the following columns:

• Site Name
  
• Site URL
  
• Purpose
  
• Target audience,
  
• Region
  
• Owner
  
• Owner Contact info
  
• Secondary owner
  
• Secondary owner contact info
  

You may have additional columns but these should be the base. Once this list is created you can then determine how content should be grouped. You want to group together sites that target the same audience. For example, if the content on the site target's users in a division your MOSS implementation would have a collection for the division. The top level site would be the homepage for the division and then each department's site would be a sub site.

SharePoint is a beast!

Trying to wrap my hands around has been challenging.
I am only looking at it from a designer’s perspective which comparatively is a minute fraction of the collective code that has gone into this product and still it is so much.
It really makes me curious to know how the product came about. Did it go thru a traditional project lifecycle with iterative design and review cycles? But I suspect that a developer built it and then when it was built that is when they called in the user experience people.