In my previous postings on webparts, i have demonstrated how to do it from scratch. In this article, i will explain how to incorporate editor for a webpart. If you have sufficient permissions, you are allowed to configure web parts. When you start configuring web parts via the user interface, a web part tool pane opens. Any configuration information  stored in the pane is persisted in the SharePoint content database. In my previous posting, you learned how to create properties that can be configured using the web part tool pane. The figure below shows an example of a web part tool pane.





Out of the box, SharePoint offers different editors for different types of data. For instance, a string property is represented by the text box editor, while a Boolean property is represented by check boxes. In this section, you will learn how to create custom editor parts, which will be shown in the web part tool pane when you are configuring a web part.

All editor parts inherit from the EditorPart base class, so that is the first step you need to take when creating a custom editor part. Editor parts look a lot like normal web parts. For instance, if you want to add child controls to an editor part, you need to override its CreateChildControls() method. The following code fragment adds a text area consisting of five lines to an editor part:

The final piece of an editor part that must be implemented is the SyncChanges() method. This method is the opposite of the ApplyChanges() method; it retrieves property values from a web part and stores them in the editor part. The following code fragment shows an implementation for the SyncChanges() method that retrieves the NormalValue property of a MyWebPart web part and stores it in the text area of the web part editor tool pane:

public override void SyncChanges()
{
}

So far, you have seen how to create an editor part. Before a custom editor part is shown in the web part editor tool pane, you need to implement support for this in your web part. In this example, we are creating a web part called MyWebPart. First, we need to add one or more properties that are read from and written to within the editor part. The custom editor part in this section expects the
presence of a NormalValue property in a web part, so that is the first thing that needs to be implemented.

The following code snippet shows how to implement the NormalValue property:

After that, you need to override the CreateEditorParts() method. This method is responsible for returning a collection of custom editor part controls that are shown in the web part editor tool pane when a web part is in edit mode. Basically, this method is used to create a new instance of one or more custom editor parts and add those to the editor part collection. This collection is used
when the web part tool pane is rendered. The following code fragment shows how to add the MyWebPartEditorPart editor part to the collection of customer editor parts that is shown when the MyWebPart web part is being edited:

and here is the complete code:

using System;
using System.Runtime.InteropServices;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Serialization;
namespace KwikSliver.Sharepoint.WebpartDemo
{
}

and below shown is the code for implementation of the MyWebPart web part. This web part displays the custom MyWebPartEditorPart web part in edit mode:

using System;
using System.Collections;
using System.Runtime.InteropServices;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Serialization;
using System;
using System.Collections;
using System.Runtime.InteropServices;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Serialization;
using Microsoft.SharePoint;
using Microsoft.SharePoint.WebControls;
using Microsoft.SharePoint.WebPartPages;
using Microsoft.SharePoint.Administration;
using Microsoft.SharePoint.Utilities;
namespace KwikSilver.Sharepoint.WebpartDemo
{
[Guid(“288802c4-4dfe-45b6-bb28-49dda89ec225”)]
public class MyWeblPart : System.Web.UI.WebControls.WebParts.WebPart
{
 }
}

and here is the end result for all the efforts made above!..

In this posting i will demonstrate how to create menu for a webpart in Sharepoint 2007.

Every web part on a SharePoint page has a web part menu that contains standard options such as the ability to minimize or close the web part. An example of a standard web part menu is shown in figure down below:

In this section, you will learn how to create custom web part menu verbs that are added to the verbs menu in a web part’s header. To start with, it is good to realize that there are three kinds of web part menu verbs:

You can create a client-side verb by creating a new instance of the WebPartVerb class. The first argument that needs to be passed to the WebPartVerb constructor for a client-side verb is the verb’s id. This needs to be unique. The second argument refers to the client-click event handler. This typically refers to a piece of JavaScript that needs to be executed once an end user clicks on a web part menu verb. The following code fragment shows how to create a client-side verb:

If you want to create a server-side verb, you need to instantiate a new WebPartVerb class, pass it a unique verb id, and specify a server-side event handler to be executed once an end user clicks on the verb. The next code fragment shows how to create a server-side verb:

The final web part menu verb type, the kind that performs both client-side and server-side actions, is created by passing a unique verb id, a server-side event handler, and a client-side event handler. You can add custom web part verbs by overriding the Verbs property of a web part and adding custom verbs to it. The code listing shows how to add custom verbs to the web part menu and define an event handler that handles a server-side verb click event:

using System;
using System.Runtime.InteropServices;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Serialization;
using Microsoft.SharePoint;
using Microsoft.SharePoint.WebControls;
using Microsoft.SharePoint.WebPartPages;
using Microsoft.SharePoint.Administration;
using Microsoft.SharePoint.Utilities;
using System.Net;
using System.Net.Mail;
namespace KwikSilver.Sharepoint.WebpartDemo
{
}

This code adds two web part verbs to the web part menu: a client-side verb and a server-side verb. Both verbs are shown in Figure.