Support dependent and computed observables
Kendo's MVVM needs to support dependent and computed observables to further assist the UI logic. As the business rules get heavier with each revision, the lack of these types are forcing to use more spaghetti jquery code to compensate. [The example below is simple, and designed in part to be in a stand alone JS file that makes the ViewModel available to all functions contained within.]
Here is the version working with KnockoutJs: http://jsfiddle.net/piercove/S6Q8D/2/
Here is a workaround with the current version of Kendo MVVM: http://jsbin.com/AZiSopO/1/edit
The workaround essentially is forcing the "change" binding onto the view model, which is ok for a work around, but should be built into the framework to be automatic.
Fyodor Soikin commented
This is just one of oh-so-many Telerik's design drawbacks.
After working (being forced to) with their products for years, I would strongly recommend to not use them at all if possible.
In the meantime, good sir Remo has built a nice Knockout-izator for Kendo here: http://rniemeyer.github.io/knockout-kendo/
Beware: because Kendo controls don't support "active" templates (yet another significant drawback), Remo had to trick it into processing Knockout bindings. When Kendo tries to render a Knockout-based template, Remo returns it a text "marker" (looking like "<!-- [template_12345] -->") and then, after Kendo has returned control, Remo picks out these markers and replaces them with instances of Knockout templates. This has a potential to create a performance penalty when overused.
Really would be better if Kendo just focused on supporting a MVVM framework rather than writing their own. It won't be as widely used or as good as the mainstream frameworks. Just stick to Knockout etc.
James Curtis commented
It added the ")" at the end above.