I visited DevConnections in Orlando about a month ago. There my colleague Todd Anglin and I held a vendor session called "Developing Rich, Responsive Applications using Telerik RadControls for ASP.NET AJAX". My team had prepared a demo for the vendor session - and we have 3 major goals when we started implementing it:

• We wanted to keep the code to a minimum (which I think we managed quite nicely). Most of the about 200 lines of server code are related to database queries, and the client-side only uses about 40 lines of code.
• We wanted it to be real-lfe and ...

It has been some time this was in the making... and as of the beginning of this week RadEditor is the editor one uses to submit community content in MSDN. Here is a hasty screenshot I made for you:



To my best knowledge, this is the fifth Microsoft team that adopts the RadEditor, yet I believe it is the first team to use it on a public Microsoft site (besides, such an important one). The other teams using the editor are doing internal MS content, and since I have not explicitly asked for permission to list their names here, I ...

Did you know that we just released our Prometheus Futures build?
And what exactly a Futures build means?
It is nothing less than a preview build for the 2008 Q1 RadControls suite release coming in April! We keep adding new controls to the Prometheus suite to get it ready for its official premiere. Three long-awaited RadControls Classic controls were ported to the suite -  RadToolbar, RadPanelbar, RadTabstrip, thus bringing the total number of Prometheus controls to twenty-two.

The Prometheus suite is more than a suite of controls. It is built on top of MS AJAX, and offers a ...

    I came across some funny event handler behavior while researching a strange problem of one of our controls (r.a.d.window) under Opera.
    Three problems are always present when writing self-contained, reusable, cross-browser DHTML controls - differences in browser APIs, consideration for third-party code on the page that might be messing with the API and - last but not least - unexpected and weird browser behavior. All these came together in the problem I am about to describe.

    Different browsers define different ways to attach event handlers - e.g. attachEvent in IE, addEventListener in Firefox and Safari, and support for ...