As title mentions bindings seems not working anymore in my app after upgrade to 2013.1.514 version of Kendo UI. What I use is commonly documented
$(document).ready(function ($) { kendo.bind($("#view"), viewModel); });loadExtPage: function (path) { //Use jQuery Ajax to fetch the template file var tmplLoader = $.get(path) .success(function (result) { //On success, Add page to DOM var index = new kendo.View($('<div />').html(result)); layout.showIn("#content", index); })}EDIT: After further observations it seems binding happening - I added alert just after binding, and view reflects viewModel properties.... but as soon as I close alert binding to viewModel seems disappears...
Thanks,
Saulius
4 Answers, 1 is accepted
Rank 1
Thanks,
Saulius
This does not sound like a known issue. Is it possible for you to isolate the problem in a sample jsbin (you can start from here). We will check it right away.
Regards,Petyo
the Telerik team
Rank 1
I was able to simulate this behavior in JSBin please use this code:
<body> <div id="main"> </div></body></html><script> var viewLoadedWithAjax = new kendo.View("<div id=\"view\">I want to say: <span data-bind=\"text: showMe\"/></div><script> var viewModel = kendo.observable({ showMe: \"Hello\"}); $(document).ready(function ($) { kendo.bind($(document.body), viewModel); }); <\/script><div>"); var layout = new kendo.Layout("<section id=\"content\"></section>"); layout.render($("#main")); setTimeout('layout.showIn("#content", viewLoadedWithAjax)', 2000)</script>SetTimeout here is for simulating ajax call, when view is downloaded i'm showing it in some layout. But binding to viewModel inside a downloaded view is broken. To solve this I now use
viewLoadedWIthAjax.render()
before showing in layout, but from souce code it seems redundant as layout.showIn actually do view.render.... So my suggestion is to check in View class(your source code) and do binding to model only if it is not null.
Best regards,
Saulius
The approach you have employed in your sample relies on ajax calls to bring rendered mix of javascript data, scripting logic, and HTML.
The SPA pattern on the other hand, revolves around the UI logic/templates being preloaded (scripts, view templates, ViewModels, event handling, etc.) while the data/content being fetched dynamically on demand, using compact JSON/XML format in order to achieve a responsive UI. Loading entire HTML blocks with scripts in it as view templates with ajax sort of defeats the purpose, and does not justify the additional complexity introduced with the SPA pattern. This being said, the design of our SPA framework is not applicable for such usage.
If your project type makes this approach a requirement, I would recommend resorting to the traditional request/response navigation model.
Petyo
the Telerik team