Web: ASP.NET AJAX

I am pleased to bring you the first of many episodes from my new video series, RadTips. These episodes will be posted regularly here on the Telerik blogs, and each will highlight a specific feature of a RadControl in a short, concise screencast. The point of this effort is to bring you quick tips on how to take advantage of the features of our RadControls without having to devote more than a few minutes of your time to the learning process. In this first episode, we'll take a look at client-side data binding with the RadGrid. There are no bells and...

We just extended RadGrid for ASP.NET AJAX with native client-side data binding to ADO.NET DataServices. Now you can use getDataServiceQuery() method and the grid will construct ADO.NET DataService style query: var northwindService = new Sys.Data.DataService("NorthwindDataService.svc"); var tableView = $find("<%= RadGrid1.ClientID %>").get_masterTableView(); northwindService.query(tableView.getDataServiceQuery("Customers"), updateGrid); All operations like paging, sorting and filtering are automatically persisted using $top, $skip, $orderby and $filter...

I've made three demos on how to use RadGrid templates to build completely client-side edit and update: - server-side GridTemplateColumn - server-side GridTableView ItemTemplate - client-side GridTableView ItemTemplate (ASP.NET AJAX 4.0...

As a strong believer in sprites, I was inspired from a question that came up in a forum thread earlier this week, namely: how to use sprites in a RadTreeView? Well, I think it's rather limiting to write only about the RadTreeView, so this post discusses the technique for all of the navigational RadControls. You can download the sample page and give it at try. Most of the code is quite straightforward - simply setting the CssClass property and a few layout adjustments. Please note, however, that this CSS is tightly bound to the skin that is currently used, so changing skins might not work...

The other day I was researching a slight RadGrid header and data cell misalignment when using scrolling with static headers. Finally, it turned out that there is a breaking change in the way Firefox 3 treat scrollable elements with an applied padding style. To be more specific, this browser version does not include the padding zone into the scrollable area, and as a result, the inner area of the element becomes smaller. Safari 2 and 3 behave the same way. Here is a very simple testing scenario:   <div style="width:400px">      <div style="width:100px;padding-right:300px;background:orange;overflow:auto">          <div style="width:500px;height:100px;background:yellow">&nbsp;</div>      </div>  </div>      The above HTML code will be displayed by Firefox 3, Firefox 2, IE7, Opera 9 and Safari...