The ASPxDocking Suite contains three components: ASPxDockPanel, ASPxDockZone and ASPxDockManager. They allow you to manage content placeholders (dock panels), which can be moved by end-users between particular areas (dock zones) within a web page. A dock panel can either be docked to a dock zone or made to float. Dock zones can be placed at any part of a page; their orientation and size are fully customizable. ASPxDockManager allows you to provide a centralized programmatic control of all dock panels and dock zones contained within a page.
This topic lists the main features of the ASPxDocking Suite components.
You can specify whether or not end-users can drag, resize, dock, and undock a panel.
Forbidden zones can be specified for a panel, allowing you to control the panel's ability to selectively dock to particular zones.
Several themes are available so you can apply an attractive design to your panel with just a couple of mouse clicks.
Customizable header and footer content. Both elements allow you to display a glyph and text (or a hyperlink). Note that you can also use templates for more flexible header and footer content customization.
Customizable appearance for the header, footer and content sections.
Control's elements can be aligned from right to left to support locales using right-to-left languages.
Panels can be arranged within a zone control one after another, either vertically or horizontally.
A zone can enlarge its size to contain a docking panel or you can disable this feature.
Different appearances for the allowed and forbidden zone states can be specified.
You can change the appearance of zones either directly via properties or by assigning a CSS class.
You can obtain collections of panels and zones within a page. The particular panel or zone can be accessed using the unique identifier (UID).
The docking layout can be fixed so that an end-user cannot change a panel's dock state and rearrange panels within a zone by dragging them.
The docking layout can be saved and restored form the previously saved.
All panels on the page can be reset to the initial (specified in markup) state.
Panel content can be load on demand via callbacks. You can specify that the panel content is always (initially) rendered inside a dock panel, it is loaded immediately after the entire page has been loaded, when a dock panel is invoked for the first time, every time after a panel has been docked, made floating, or dock state has been changed.
Client-side events allow you to respond to panel resizing, visibility state changes, dragging, and docking.
You can use client-side API to show, hide, dock, and undock panels, specify their position relative to other HTML elements and change their content.
Was this page helpful?
Thanks for your feedback! Any other suggestions? Tell us here.