This is an opinionated guide prescribing the ideal usage of Kendo UI mobile widgets and application tools for building web platform sites or applications to be run on phones and tablets.
Your new post is loading...
Your new post is loading...
Current selected tag: KendoUI. Clear.
wingspan-forms is a a dynamic form library for Facebook React, providing abstractions for building dynamic forms and controlled grids. Widgets are provided by Telerik's KendoUI. wingspan-forms is about half "Kendo-React adapter", and half general functional-programming friendly form abstractions that aren't coupled to the underlying widget implementation. The higher level of abstraction is the important bit - this level of abstraction isn't possible in "just Kendo" or any other OOP style widget library.
Much of that excitement is due to the fact that React views the UI differently that what we're used to. You don't mutate the DOM directly - instead React components render to a virtual DOM. This virtual DOM diffs your new changes and computes the minimum number of steps to update the actual DOM, which is then effectively "patched" only with what changed.
However, every web UI library/framework I've worked with up to this point mutates the DOM directly. If I want to take advantage of existing UI widgets from other libraries, while still using React, can I do so?
The answer is yes.
A project to create a complete and robust set of Knockout.js bindings for the Kendo UI widgets.
Knockout.js is an open source library that supports declarative data binding, dependency tracking, and automatic UI updates.
Kendo UI, by Telerik, provides fast, clean, and configurable HTML5 UI widgets as part of a jQuery-based framework to support modern web development.
With AngularJS and ASP.NET MVC, we now have an MVC pattern and architecture for both on the client and server. What do we do and/or how do we approach this? Well one can argue we don’t use any of the MVC architecture on the server and build out a full-fledged AngularJS front-end application and only use make async calls to Web API for all things that absolutely need to be on the server e.g. CRUD, workflows, business logic, etc.
Now, there’s absolutely nothing wrong with this approach, and for the most part a lot of heavy front end SPA’s are built this way in ASP.NET MVC. However, with all the .NET, ASP.NET and AngularJS goodness, why not leverage the best of both worlds? Again, there’s absolutely nothing wrong with building a pure AngularJS application and only using Web API, but for this blog post we’ll go over patterns of using the best of both worlds along with integrating AngularJS with Kendo UI.
You already know that Kendo UI has magnificent widgets. UI is in the name, and Telerik has a long proud history of building amazing UI components. What you may not know, is that you can actually use Kendo UI (specifically MVVM) to work with plain HTML to construct your own widgets. This is sort of like running on the bare metal, but it’s tons of fun and thanks to Kendo UI’s streamlined MVVM, it’s quite easy as well.
Knockout provides the ability to loop over a collection by implementing a for iterator. The power of this really can’t be underestimated since it allows you to take collections and render them visually with HTML getting fine grained control over how each of the items will look. The only problem with this, is that for loops can get unwieldy and don’t mix very gracefully in HTML attributes. This earned some bad rep for Knockout in it’s early days through no fault of the framework itself. Regardless of it’s tendency to clutter HTML, it’s a powerful construct that is noticeably absent from Kendo UI’s MVVM implementation. Or is it?
This article give a example of use of it with the WEB drop-down list from Telerik Kendo. The example made use of typescript to programming the Kendo drop-down list and it uses kendo MVVM to operate the control and a WEB API to get the information from a remote source.
Kendo UI is an amazing framework that does a lot more than just make your website pretty. I have decided to do a series of posts on using the entire package to put together a complete blog site using Kendo UI, Twitter Bootstrap, and Everlive.
To get started lets just look at what each piece of the pie is and how they will be used to work together and how they will help us reach our final goal.
Now we have all seen the standard contact form on a site and I think they are good to have. So in this installment I will show you how to put together a contact form and wire it up using Kendo UI's MVVM. Along the way I will show you how to use the Kendo UI Validator's.
The big star of the show will be hooking your form data up to Everlive content item and saving the data to your cloud storage and then sending you an email from your site. Now I would normally not push data from a contact form into a database, but for this tutorial we will do it just cause we can.
In this article we will learn to write mobile apps using native, hybrid and responsive development techniques for popular device platforms like iOS & Windows Phone for now and later Android & Black Berry.
The summary of the topics covered:
iOS Native App -> with Intro to Objective-C
In this course we will explore kendo UI in details. We will talk about each widget and see how it works. We will start with the html part and initializing the widget. Once we get that up and running, we start experimenting with the properties and functions. For the events, we will log them to div under the widget to see what events are triggered and when.
As a fan of both Firebase and Kendo UI, I was compelled to build my peanut butter and chocolate scenario; two great tastes together as one. The end result was kendo-fire, a set of bindings for building applications that utilize Kendo UI and Firebase at the same time.
The Q1 2014 release of Kendo UI added support for real-time data through the introduction of a set of push callbacks to the kendo.data.RemoteTransport. Currently, Kendo UI supports WebSockets and SignalR out-of-the-box. However, this functionality can easily be extended to other protocols and providers, like Firebase, through a custom RemoteTransport.
Today I launch a new series of postings, bringing together two themes I’ve been developing for the past few months: AngularJS and Kendo UI. These technologies go together like peanut butter and chocolate, and both share two characteristics that are critical to this series:
The technology is hot, desirable and useful.
Part 2: Binding With ng-model and Moustaches
Jan Hesse's insight:
Hybrid development, or the approach of building native apps using Web technologies, has gone through its fair share of highs and lows. But, despite high-profile abandonments from the likes of Facebook and LinkedIn, hybrid development continues to be used by a substantial number of developers.
Is hybrid as a platform growing or shrinking? Is performance still a limiting factor for hybrid apps? In this article we’ll attempt to answer those questions. We’ll look at where the hybrid ecosystem is today, and where it’s heading.
a dynamic form library for Facebook React, providing abstractions for building dynamic forms and controlled grids. Widgets provided by Telerik's KendoUI.
Helping you select a cross-platform mobile framework - Apps using jQuery Mobile, Sencha Touch, Titanium and more
Some of the frameworks deliver a native user interface, whereas others construct a native-like interface using HTML5 technologies. When selecting a framework it is important to test the end-user experience that the framework delivers and ensure you are happy with any compromises.
The code-sharing which can be realistically achieved with each framework varies considerably. To aid in this comparison there is a build script which produces code metrics for guidance. Although, as developers I am sure you are aware that lines-of-code metrics are flawed.
It is also worth investing quite a bit of time familiarising yourself with tools provided by each framework. The cost and quality of these varies considerably.
Introducing The HTML5 Mobile Challenge
We created the HTML5 Mobile Challenge to put perceptions about HTML5 and mobile to the test. Not just a blanket generalization, but a hands on experiment so we could start with the raw senses and move up to the truth. We gave savvy developers two seemingly identical applications, and asked them to advise us on which one was native, and which one was a hybrid application running in a browser.
The proof is in the video. Once you tell someone that an app is native or hybrid, they make immediate assumptions about it based on their perceptions. Even when there is no native application at all.Introducing Cuteness
In order to be able to challenge perceptions, we first had to find out if the rumors about HTML5 were true. Could we build a mobile app with HTML5 that was indistinguishable from native? We've heard a lot about how it couldn't be done, so we decided to find out for ourselves.
Over the last few months, we put our money where our mouth was - on HTML5. We sat down, designed an app, and began to build it using our own tools and the HTML5 platform. The result was a demo app called “Cuteness”.
Cuteness is a Reddit reader (so named because it only allows you to read the 'aww’' subreddit) which aims to take a hard look at some of the most tenuous areas of the mobile web.
It’s probably important you have at least a high level picture what an SPA architecture looks like now that there is quite a bit more design work involved on the client side especially with more and more implementations are around SPA and patterns like MVVM; so hence this post. Obviously there is no such thing as one size fits all especially when it comes to architecture, so feel free to omit or add to the architecture based on your specific needs.
Client Layer (HTML5 Browser)
Web Layer (Server)
This blog post compares the same twitter search application written with both Knockout and Kendo in order to highlight the strengths and weaknesses of each framework. I’ve always been a big fan of Knockout, most likely because it reminds me of Silverlight (rest in peace).
More recently I have been dabbling with the use of Knockout for writing mobile applications. Because Knockout is an MVVM framework and doesn’t have any UI components of its own, I used a combination of jQuery Mobile (jQM) and Knockout. I must admit, the integration of these two frameworks wasn’t entirely painless!.
It is the integration pain I experienced with jQM and Knockout that has resulted in my interest in KendoUI.