Telerik blogs
  • People

    telerik skins survey

    I’ve been having this nightmare recently that we’re off track with what customers are looking for in terms of interface design, and I guess the best way to find out how we’re doing is to ask you guys. So I’ve set up a short online survey for all willing to help us feel where the industry is heading and provide feedback for what they need. Your feedback so far is truly encouraging and will be instrumental in crafting our future plans for skin development, interface design and visual presentation of all telerik components. I would strongly encourage all of you...
  • Desktop WPF

    WPF in action - part 1: Designer's look on WPF

    I am yet to grasp the marketing behind Microsoft naming conventions - usually a beta program would jump start with a great name, the official launch would kill it in a dull title, and things would finally settle down with an abbreviation that is actually pronounceable. Naming conventions aside, the upcoming Windows Presentation Framework (WPF), formerly known as Avalon, holds promise to become the next buzzword of the industry - even if someone adds to it another sentence before the official roll-out with Windows Vista in early 2007.From a designer's point of view, the next-generation interface for Windows is all...
  • Web ASP.NET AJAX

    IE Memory Leak Best Practices with AJAX in Mind

    Am I getting obsessed with memory leaks?  Give me a non-leaking browser and I'll cut it out .Yesterday I was hunting for a hard-to-find memory leak with r.a.d.treeview.  Our component cleans up its DOM element references and DOM event handlers when it is being destroyed.  Control destruction and resource disposal occurs on two occasions:  when the page unloads and when the control is updated by an AJAX call (r.a.d.callback, Atlas, etc -- the mechanism is framework-agnostic).  Now the treeview, being a good citizen, follows the leak prevention pattern of keeping references to DOM elements to a minimum.  Most of the...
    April 28, 2006
  • Web

    The invisible memory leaks in MS Internet Explorer

    Oh boy, not another memory leak post!  We already got a couple here and there.JavaScript development is so frustrating at times that every little victory counts.  The seemingly memory-managed, easy-to-write script language sometimes is harder than C++, and believe me, I've had my fair share of C++, Win32  and COM development.  As if it's not enough that you have to deal with each and every browser's way of implementing the "standard", but now you have to manage and free your own memory.Memory leaks have not been a big problem most of the time.  Well, a leaked <div> or <td> here or...
    April 10, 2006
  • Design

    Telerik skins photoshop sources.

    Thinking how to make your life and our ROI targets easier, we decided it’s a good idea to provide for download the Photoshop sources of our components’ skins. So we sat down and toiled relentlessly to tame the mess of untitled layers into something of actual business value – the result is a section at http://www.telerik.com/skins with free downloads of the Photoshop sources for the most requested telerik skins. Pure design goodness for you to customize and build upon. Remember this section when the time comes to design your next application – this time you can jump start with a ready...
    March 12, 2006