The primary component of the widget is the control itself. It represents the frontend functionality that the end-user interacts with on the website.
It is defined either as a standard user control (.ascx) and its associated code-behind file (.cs) or a custom control (.dll) and its associated template file (.ascx).
Widgets are generally made up of different HTML elements and ASP.NET controls, such as textboxes and buttons, and can use more complex controls, such as Telerik RadControls.
All the backend functionality that the user uses to set the widget properties is called control (widget) designer. The default Sitefinity CMS widget designer displays all public properties of the widget as input fields.
A control designer has the following elements:
This is the class file that defines the control designer and is used to wire-up all of the designer elements. It must inherit from the ControlDesignerBase class.
The template is an .ascx file that represents the actual editor that is displayed to the user. It is made up of standard HTML elements that are mapped to the properties of the widget.
For the script file to function properly, perform the following:
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2020 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity