Telerik blogs

    Put your ASP.NET menu on a healthy diet -- introducing the lightweight render mode for RadMenu

    Slowly but surely, we are rolling out our lightweight initiative to more controls. This time it's Telerik’s ASP.NET Menu. Skip after the break to learn what we've changed.
    October 31, 2013

    Telerik RadControls for ASP.NET are getting a bit Sassy

    Writing CSS tends to be mundane for the most part of it. Yes, it has truly exciting moments in a twisted kind of way, but for the majority of the time it's the same thing line after line, after line, after line… Thankfully, we have Sass
    April 02, 2013
  • Release

    A Sneak Peek at our ASP.NET AJAX RibbonBar development

    A few months ago, I blogged about Telerik’s ASP.NET RibbonBar control (or just ribbon for short) in general: why use it; a few words about the ribbon spec; improvements we have made and future plans we have for it. Now, few days after the 2012 Q3 release, I am blogging about our progress in this area, as well as bringing up some other lesser known features of the ribbon. What's old new in the Ribbon I did mention this in my previous post, but perhaps I did not emphasize it enough: apart from complying with the MS specs more, we introduced two major features for...
    November 01, 2012

    The Story of the Ribbon so far and to come...

    The ribbon (or RadRibbonBar, as we have named it) is among the most tempting-to-use looking and yet somewhat neglected controls. True, it has received some Microsoft love with being the core command component in the Office suite, as well as being more deeply integrated in the soon-to-be-released Windows8, but overall it's not been used that much. Main reason being “why use it”. That, by the way, is an excellent question. So why use the ribbon? To answer that, let's first analyse the control and its purpose: it looks like a tabbed command area; a tabbed toolbar if you will. For the most part,...
    August 23, 2012

    Separate Skin Assembly in RadControls for ASP.NET AJAX with Q3'11

    Probably all of us have identified at some point the following trend in software development — newer version usually means bigger assemblies. Sure, some of the new stuff is features that we use on a daily basis; but some of the new stuff is just eye candy that we don't always use. In fact, wouldn't it be nice if we could get just the software with the default looks; get the job done then and, if needed, add that sweet UI candy to it later? And in order to tackle this problem — maintain a reasonable file size of the main Telerik...
    November 15, 2011