Telerik blogs
  • Web ASP.NET AJAX

    Glassy buttons, interrupted?

    Has the time come to challenge the top place of glassy look in today’s web notion for haute couture? What could possibly act cooler than a glassy button on your web site? Admit it, even if you never had it, at one point or another you secretly craved for one. One of those fat, professional looking glassy buttons that scream out loud style & grace and are said to sky-rocket click through rates. Everyone’s got it - for the last couple of years, web interface has been all about this glassy feel – ironically enough, with the fall of the...
    March 06, 2006
  • Web

    Adding controls to Visual Studio Toolbox

    The Problem As Rumen said, adding controls to Visual Studio toolbox can be a tedious procedure. That's why r.a.d.controls are automatically added in the toolbox during installation. This makes it easier for the developer to start using them. However there is a catch - no control is added in Visual Studio 2005... Our toolbox adding code runs without an error but ... nothing happens. Several months ago I found the following forum thread which basically said that the code used to add toolbox items in Visual Studio 2003 will simply not work in Visual Studio 2005. And it is 100% right! We decided to abandon this...
    March 01, 2006
  • Web ASP.NET AJAX

    Importance of meaningful error messages

    The other day I had a very strange Visual Studio 2005 experience. I was testing the new design time capabilities of r.a.d.tabstrip and something went extremely wrong. My test environment consists of a WebControlLibrary project (the control itself) and a WebSite with a single aspx page containing nothing but a humble r.a.d.tabstrip. The site has a project reference to the web control library so it gets rebuilt whenever I build the site. So far so good. Here is the fun part - whenever I rebuilt the site and refreshed the page I received the following error:Ok, i said to myself, it's debugging time. I...
    February 07, 2006
  • Productivity Testing

    Two types of jsUnit tests

    I am a big jsUnit fan. I can't imagine what JavaScript development would be like if that tool did not exist. We all know that code without proper unit test coverage is legacy code. It is a time bomb waiting to go off in the hands of the developer that touches it next. Over time I have noticed a pattern in my jsUnit usage. I usually wear one of two testing hats when writing tests:The browser compatibility hat. Most developers know how to do things in Internet Explorer, and Gecko-based browsers. Those differences are widely known and people are used to writing...
    January 18, 2006
  • People Accessibility

    Making ASP.NET XHTML 1.1 compliant

    As you may know, all components from the r.a.d.controls suite render XHTML 1.1 compliant output. We wanted to promote it in a way that all users can click a button in our online examples and see for themselves that everything validates perfectly. W3C provides an online validation service (http://validator.w3.org) so it should not be that hard. Unfortunately ASP.NET 1.x complies with *NO* HTML standard ever approved by W3C. ASP.NET 2.0 was first XHTML 1.1 compliant, but then in the official release Microsoft fell back to XHTML 1.0 transitional which is less restrictive. I made a couple of Google searches and found other people...
    December 09, 2005