Did you know? DZone has great portals for Python, Cloud, NoSQL, and HTML5!
HTML5 Zone is brought to you in partnership with:

My name is Sagar Ganatra and I'm from Bangalore, India. I'm currently employed with Adobe India and I work there as a ColdFusion Engineer. At Adobe, I have worked on various features of ColdFusion and ColdFusion Builder. I'm very much passionate of web technologies and have a very good understanding of jQuery, Flex, HTML5, Java and of course ColdFusion. Sagar H is a DZone MVB and is not an employee of DZone and has posted 29 posts at DZone. You can read more from them at their website. View Full User Profile

Using Source Binding and Templates in KendoUI

06.27.2012
Email
Views: 876
  • submit to reddit
The HTML5 Microzone is presented by DZone and Microsoft to bring you the most interesting and relevant content on emerging web standards.  Experience all that the HTML5 Microzone has to offer on our homepage and check out the cutting edge web development tutorials on Script Junkie, Build My Pinned Site, and the HTML5 DevCenter.

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:

<!DOCTYPE HTML>
<html>
    <head>
        <script src="../../js/jquery.min.js"></script>
        <script src="../../js/kendo.all.min.js"></script>
<script>
$('document').ready(function() {
viewModel = kendo.observable({
optionsData: [
{optionValue:1, optionName: "test1"},
{optionValue:2, optionName: "test2"},
{optionValue:3, optionName: "test3"}
]
});
kendo.bind($('select'),viewModel);
});
</script>
    </head>
    <body>
     Select example:
<select data-template="select-template" data-bind="source: optionsData">
</select>
<script id="select-template" type="text/x-kendo-template">
<option data-bind="attr: {value: optionValue}, html: optionName">	
</option>
</script>	
    </body>
</html>

 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.

Published at DZone with permission of Sagar H Ganatra, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)

HTML5 is the most dramatic step in the evolution of web standards. It incorporates features such as geolocation, video playback and drag-and-drop. HTML5 allows developers to create rich internet applications without the need for third party APIs and browser plug-ins.  Under the banner of HTML5, modern web standards such as CSS3, SVG, XHR2, WebSockets, IndexedDB, and AppCache are pushing the boundaries for what a browser can achieve using web standards.  This Microzone is supported by Microsoft, and it will delve into the intricacies of using these new web technologies and teach you how to make your websites compatible with all of the modern browsers.