• .NET Mobile Web Kendo UI

    Post Google I/O Rundown

    That's a wrap for Google I/0 2013. Here are the highlights and all things Kendo UI at Google I/O.
  • .NET Mobile Web Kendo UI

    Video Blog: 2-Way Sync With KendoUI-Backbone

    In this short video, I'll show you an update on what I've been doing with the KendoUI-Backbone integration project, with 2-way synchronization between a Backbone.Collection and a KendoUI DataSource.
  • .NET Mobile Web Kendo UI

    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.
  • .NET Mobile Web Kendo UI

    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.
    June 06, 2013
  • .NET Mobile Web Kendo UI

    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.