Skip to main content

Using Source binding and templates in KendoUI

Yesterday I explored the MVVM design pattern in Kendo UI that allows the model data to be separated from the view. Also, whenever data in one of them changes it is reflected in the other. Today I was exploring various data bindings that can be used and one that caught my attention was the source binding. The source binding allows you to set the HTML content of the target element by rendering a Kendo template with a View-Model value. For example, say you have a combo box (select tag) and you want to populate it with data (option tags), then instead of writing several option tags you can define a template and provide source binding for the same. This will show a list of options from the ViewModel.

Here's the code:

There are several things going on here. The ViewModel object (kendo.observable) is created which contains a key optionData which is an array of JavaScript objects. Each one these object defines the option value and the html data that it should contain.

When you observe the view part defined in the body; it has a select tag with a data-template attribute. The value provided in the data-template attribute should match with the id of the script tag that contains html content that should be inserted inside the select tag. Here that html content or the template contains the option tag. Also, the select tag defines the data-bind attribute wherein the source binding referring to the optionData is defined. The Kendo template is a script tag with the id same as the data-template value specified in the select tag and with attribute type defined as 'text/x-kendo-template'. The body of the script tag contains the template (option tag) which will be iterated over for the number of JavaScript objects defined in the source. The option tag defined in the template also has the data-bind attribute which defines the binding for the value and the html attribute. 

Now when the page is rendered, you would be able to see a select tag with three options - ['test1','test2','test3']. Similarly this can be applied to other tags (ordered\un-ordered lists) where the base template is defined and its value is bound to a ViewModel.

Comments

  1. The source binding sets the HTML content of the target element by rendering a Kendo template with a View-Model value. If the View-Model value changes the HTML content of the target element will be updated.

    ColdFusion Web Development

    ReplyDelete
  2. Yes that's what I've explained in this post as well as in the previous post.

    ReplyDelete

Post a Comment

Popular posts from this blog

Adding beforeRender and afterRender functions to a Backbone View

I was working on a Backbone application that updated the DOM when a response was received from the server. In a Backbone View, the initialize method would perform some operations and then call the render method to update the view. This worked fine, however there was scenario where in I wanted to perform some tasks before and after rendering the view. This can be considered as firing an event before and after the function had completed its execution. I found a very simple way to do this with Underscore's wrap method.

De-obfuscating javascript code in Chrome Developer Tools

I had blogged about JavaScript debugging with Chrome Developer Tools  some time back, wherein I have explained how these developer tools can help in debugging javascript code. Today Google Chrome 12 was released and my Chrome browser was updated to this version. As with every release, there have been some improvements made on performance, usability etc,. One feature that stood out for me is the ability to De-obfuscate the javascript code. What is Minification? Minification is the process of removing unnecessary characters such as white spaces, comments, new lines from the source code. These otherwise would be added to make the code more readable. Minifying the source code helps in reducing the file size and thereby reducing the time taken to download the file. This is the reason why most of the popular javascript libraries such as jQuery are minified. A minified jQuery file is of 31 KB in size where as an uncompressed one is about 229 KB. Unfortunately, debugging minified javascript f

On GraphQL and building an application using React Apollo

When I visualize building an application, I would think of using React and Redux on the front-end which talks to a set of RESTful services built with Node and Hapi (or Express). However, over a period of time, I've realized that this approach does not scale well when you add new features to the front-end. For example, consider a page that displays user information along with courses that a user has enrolled in. At a later point, you decide to add a section that displays popular book titles that one can view and purchase. If every entity is considered as a microservice then to get data from three different microservices would require three http  requests to be sent by the front-end app. The performance of the app would degrade with the increase in the number of http requests. I read about GraphQL and knew that it is an ideal way of building an app and I need not look forward to anything else. The GraphQL layer can be viewed as a facade which sits on top of your RESTful services o