1) The first example is a custom field type that you can add to any document library and that returns the main properties of any document by
clicking on it in a fast and user-friendly way. Thanks to the jQuery code embedded in the CAML of the custom field type, the properties are returned via an AJAX query that calls lists.asmx to get the properties. 
This example is the main topic of the video and is rebuilt from scratch.

2). The secund example will be available for download and is overviewed during the video. It's a custom SharePoint calendar where users can type locations in a textbox. All the matching events are highlighted within the calendar directly (they blink) and direct links to the events are shown above the input textbox. 

Again, same principle than for the first example (query to lists.asmx) but this time the jQuery code is isolated in a separate JS file and both the jquery javascript file and the custom one are included OnPreRender of the custom calendar control.

To watch this video, click here.

TABLE.ms-recyclebin TD {
     background: #000000 url('<image_path>') repeat-x;
     border: 1px solid #FFFFFF;
} 

TABLE.ms-recyclebin TD A{
     color: #FFFFFF;
}

listsWS. Lists   listService = new listsWS. Lists() ;
listService.Url =  "http://litwareportal/<your_site>/_vti_bin/lists.asmx" ;
listService.Credentials =  new  System.Net.NetworkCredential( "Administrator" ,  "Pa$$w0rd" , "LITWAREINC" );

XmlDocument   doc =  new   XmlDocument () ;
XmlNode   viewFieldsParent = doc.CreateElement( "ViewFields" );
viewFieldsParent.InnerXml =
"<FieldRef Name=\"Author\"/>" +
"<FieldRef Name=\"BookName\"/>" +
"<FieldRef Name=\"PageCount\"/>";

XmlNode listItems = listService.GetListItems( "Books" ,  "" , null, viewFieldsParent,  "0" , null,  "" );

foreach  ( XmlNode   item  in  listItems.SelectNodes( "//*[local-name()='row']" ))
{
Console .WriteLine( "Author: "  + item.Attributes.GetNamedItem( "ows_Author" ).Value);
Console .WriteLine( "Book Name: "  + item.Attributes.GetNamedItem( "ows_BookName" ).Value);
Console .WriteLine( "Page Count: "  + item.Attributes.GetNamedItem( "ows_PageCount" ).Value);
Console .WriteLine( "#####################################" );
}

Console .ReadLine();

After you install Windows SharePoint Services 3.0 SP1, declarative workflows will not start automatically if the following conditions are true:

1. The Windows SharePoint Services Web application runs under a user's domain account.
2. The user logs in by using this domain account.
3. The site displays the user name as System Account.

Here is the link to the solution :  http://kbalertz.com/947284/declarative-workflow-start-automatically-after-install-Windows-SharePoint-Services-Service.aspx