Apply to

Overview

A console skin is the same type of control from which other controls can inherit appearance settings. When a control skin is applied to a control, the target control inherits appearance settings from the skin control.

You can use EO.Web Control Builder to create a control based on a built-in skin, update the appearance properties and save it as another control or control skin. This section covers these topics:

Create a Custom Skin

Control Builder can be used to create a custom skin. The process of creating a skin is the same as creating a control, you can use Control Builder to save it as skin.

Once you have created a custom skin, you can apply it by two simple steps:

1. Load the skin into memory and assign unique skin ID.
   Each control has its own "LoadSkin" method, e.g, menu's method is LoadMenuSkin. A skin should be loaded only once so it's recommended to do it in Application_Start function.

   Note Built-in skin is automatically loaded. This step can be skipped.

2. Set control's ControlSkinID to the skin ID.

Use Built-in or Custom Skin

Each EO.Web control offers several built-in skins. It's recommended to always create a control based on built-in skin, which has predefined styles.

A control can use a skin in two ways:

• During design time, in control builder, use built-in skin as template to create a control.
• During run time, use built-in or custom skin to switch control's appearance by using ControlSkinID property.

During rendering, EO.Web controls apply skin's appearance setting by merging the skin control and the target control's appearance settings. When a property is specified both in skin and target, target control's value takes precedence.

The merging occurs during the rendering process after the view state has been saved, any changes to the ControlSkinID property will be saved into the view state (if view state is enabled).