• .NET Mobile Web Kendo UI

    Kendo UI SPA: Screencast And Getting Started

    May 16, 2013 Share
    With the Q1 2013 release of Kendo UI, there were several new components added to better facilitate Single Page Application (SPA) development. Since the release, I've been building sample applications, writing blog posts and creating screencasts to cover these new framework pieces. Find the best places to learn and get your SPA on, with these links.
  • .NET Mobile Web Kendo UI

    Kendo UI At Google IO

    This week, some of us at Telerik are attending Google I/O in San Francisco. We're not just attending though, we've been invited into the Sandbox for the second year in a row to show off some of the really amazing things that the engineering team has been doing both with HTML5, and Mobile. This includes not just Kendo UI, which has become a world class framework for HTML5 web and mobile development, but also the brand new Icenium platform for seamlessly building cross-platform mobile applications built on Cordova.
  • .NET Mobile Web Kendo UI

    Announcing the Kendo UI Q1 2013 Service Pack

    Over the last few months, we’ve been working hard to deliver you an awesome Q2 2013 release (which you can read more about, here. Along the way, we figured today was good time to drop a Service Pack for Q1 2013, which includes a bunch of new features and a boatload of fixes. In this blog post, I’ll highlight a few of things we’ve added in this release.
  • .NET Mobile Web Kendo UI

    A Day At The SPA With kendo.Router

    This luxurious SPA life can be difficult. It can lead to some #FirstWorldProblems. What if I want to get started with my treatments and therapy, but I have to stop in the middle and come back later? I don't want to re-start the procedure that I've already started. I would rather return to the same therapist and pick up where I left off.
  • .NET Mobile Web Kendo UI

    RequireJS Fundamentals

    If you have been following JavaScript development, you might have seen a lot of posts on modules. It's a hot topic in JavaScript and it's easy to jump on a bandwagon. The truth is that the problem that needs to be solved is very fundamental to the success of your code.