Telerik blogs

Latest

  • Web

    The Attack of the Light-Rendered or how Lightweight beats Heavyweight with CSS3 and HTML5

    Lightweight rendering mode is available for five more controls – RadCalendar, RadDock, RadFormDecorator, RadToolTip and RadWindow. Enjoy the benefits from the new HTML5 semantic rendering and the power of CSS3 the Q2 2013 release of the RadControls for ASP.NET AJAX will bring to your application!
    March 17, 2025 6 min read
  • Web

    Animating the RadBusyIndicator while the UI thread is frozen

    One of the challenges when developing an application is to give visual indication while a long running process is occurring. In Silverlight this can be easily achieved using the RadBusyIndicator control. However, the UI thread sometimes gets frozen.
    May 27, 2021 2 min read
  • Web jQuery

    jQuery Context Overload

    I'm sure most of you can relate to that feeling you get when you learn about something that you're pretty sure everyone else already knows about. Something fundamental. I remember when I learned that I could test for nullable integers in C# by using hasValue. Or when I first learned that you could use array notation in JavaScript to dynamically access properties and methods. Sometimes we don't talk about these things. We sort of just look around to make sure no one was watching when we were the last to find out.
    May 27, 2021 6 min read
  • Web

    Asset Management, the Status Quo and Areas Of Opportunity

    Why do we organize assets the way we do? It must be rooted in tradition. Back when the internets were first getting started, and the world wide web was at version “1.0”, we just didn’t have that many .css or .js files to organize. So we put all our .css files in a public directory called “assets/css” and all our .js files in a public directory called “assets/js”, and we were done ... but there must be a better way.
    May 27, 2021 5 min read
  • Web

    To Navigate, Or Not To Navigate?

    Routers are powerful tools in Single Page Applications, and Kendo UI's router provides an API to wrap up this power. But the API hides a lot of potential complexity and performance issues if you're not careful. Calling the navigate method without regard for the current context of the application and whether or not that context is changing can result in unwanted re-rendering of the entire application. This can reduce the responsiveness of the app, waste time re-drawing content that isn't changing, and cause a lot of flickering on the screen - and none of this is desirable from a user's perspective.
    May 27, 2021 8 min read