CAB Whitepaper

Implements the DockingManager as a workspace which shows the smartparts as docked windows. This is implemented based on the window workspace. Each smartpart gets converted into a Form object and then shows up as a docked window. The DockingSmartPartInfo class defines most of the properties that would be normally accessible in normal Windows Forms designed application.

Implements the GroupBar as a workspace which shows the smartparts as grouped/stacked windows. The GroupBarSmartPartInfo class defines several properties through which the smartpart’s visual behavior can be changed.

The TabControlAdvWorkspace implements a workspace which shows smartparts as tabbed pages inside a TabControlAdv. Most of the properties of TabControlAdv have been added to the TabControlAdvSmartPartInfo that would help customizing the workspace accordingly. Even TabPrimitives can be added to the TabControlAdvWorkspace through the TabPrimitiveInfo collection found in the properties of TabControlAdvSmartPartInfo class.

The TabbedMDIManagerWorkspace implements a workspace which shows smartparts in TabbedMDI forms. A Windows MDI Form is passed as an instance to the TabbedMDIManager. It acts as a container for all the Forms that are added in the Host MDI Parent Form and shows that in a Tabbed manner. Features like TabAlignment, TabStyle and others are set through the TabbedMDIManagerSmartPartInfo Class.

The SplashPanelWorkspace implements a workspace which shows controls with SplashPanel properties. It maintains an internal dictionary list, which contains the list of controls that have been already added to the workspace. The control that is going to be added is converted to a SplashPanel object and then the corresponding properties are applied through SmartPartInfo object.

It implements a workspace which shows SmartParts in TaskPages inside the XPTaskPane. It maintains an inner dictionary list, which holds the reference to the list of task pages pushed into the XPTaskPane container. The XPTaskPaneSmartPartInfo class has properties that allow the user to show the smartpart at the beginning of the XPTaskPane control list. It inherits the SmartPartInfo class and thus provides basic functionality of this class.

Implements a workspace which shows smartparts in SplitterContainerAdv Control. The SplitterContainerAdvSmartPartInfo class has a property called PanelSide, that defines on which side of the panel should the smartpart be shown.

Implements a workspace which shows smartparts in DockingClientPanel. The main feature of this workspace is that it would automatically reposition this child controls present in its inner collection when the client changes during docking/undocking operations. Controls thus placed on this workspace avail a static boundary for implementing any required layout management.

UIElements

The look and feel of Office2007 controls can now be included in any CAB project using Essential CAB Enabling kit UIElements. It includes the following,

The following objects can be registered as an extension site,

• TabStripItem.Panel
• ToolStripEx

The following objects can be registered as an extension site,

• BarManager
• Bar
• ParentBarItem
• BarItem

Loading of BarItems in the menus can also be done using an XML file/objects (refer documentation). The Essential CAB Enabling Kit includes a BarItemSchema which defines the structure of the XML file. This enables very easy customization and quick structuring of the BarItems.

The following objects can be registered as an extension site,

• StatusBarAdv
• StatusBarAdvPanel

The following objects can be registered as an extension site,

• XPTaskBar/XPTaskBarBox
• XPTaskBarItem/Panel

Syncfusion controls that are supported as UIElements by Default

The following controls can be registered as an extension site as it is done for Microsoft menu items. Since these controls inherit from the ToolStripItem family, it can be easily used with the already defined UIElement classes from the CAB architecture.

• StatusStripEx
• ToolStripEx

Other Syncfusion controls that can be used in CAB architecture

The CAB architecture is so extendible that any given control can be used as a workspace. The Essential CAB kit is an extension to this and provides easy and seamless creation of workspaces that are commonly found in developing large Windows Forms projects. Other Syncfusion controls that can be used are GridControl, GridGroupingControl and DiagramControl.

• NetworkFlowModel sample demonstrates the use of DiagramControl, which is available in the Essential CAB kit.
• Outlook2007 sample demonstrates the use of GridControl.

Feature Requests

Provide loading of all the UIElements through XML

• RibbonControlAdv
• StatusBarAdv
• StatusBarEx
• ToolStripEx