MVVM examples

[Timo]

Hi. 

Are there any sketches on how the coming MVVM API will look like? With the current feature set Kendo UI doesn't look like a full solution and I couldn't much docs on how to integrate it with JavaScript MVC frameworks like Backbone.

Br,
Timo Westkämper

[Atanas Korchev]

Hello,

 We can't yet share any info about the MVVM implementation. We would release a beta though in the coming months.

Regards,
Atanas Korchev
the Telerik team

[LessX]

What day will be the release that will contain the MVVM? 

[Dustin]

The Kendo UI Web Webinar is Feb 22nd for Q1 2012. Usually you guys release your quartely releases right before the quartely webinars. Does this mean that MVVM support will be included in Feb's Q1 release? If so, that is less than a month away and there is still no beta yet available.

Can someone reply with detail and no vague answer for I am going to be doing a redesign on our site very soon and the importance of this information is critical for decisions need to be made on whether to use another MVVM like library (i.e. KnockoutJS) or Kendo UI's built-in MVVM if it is available.

[Atanas Korchev]

Hi,

 The Q1 2012 Kendo release is due late March. The beta is due at the end of February. If you need to make a decision earlier you should probably start with KnockoutJS.

Greetings,
Atanas Korchev
the Telerik team

[LessX]

I hope the syntax is similar to, or compatible with knockoutjs. Or integrate that library.

[Joachim]

I hope not. Knockout uses ugly wrappers on the view model. The approach of Angular and Google MDV is much cleaner. Besides, JsViews and Angular is *much* faster.

[LessX]

these are not the same concept.

angularjs is mvc framework 
knockout is mvvm framework (focus in model only) 

and it is true that you said, but:

The way events from bindings are dispatched. If I'm not mistaken:

ko = listener per binding. (very important with respect to performance of the memory)

ng = scope (loops until all bindings within scope are handled ... scales well for larger apps)

[Joachim]

Although their under the hood binding mechanism is different, I would argue that they indeed belong to the same conceptual family. They both provide declarative two way binding between view model and view as opposed to MVC patterns or templating engines that lacks the notion of a view model.

Angular, JsViews, Knockout and Google MDV adheres to the category of recent MVC patterns that have an abstract view model in the form of an object tree that drive the views. The view to view model has two way declarative binding and your application code update the view via the view model. Similarly, the view communicates with the application via the view model.

Knockout, JsViews and MDV stays clear of anything not dealing with the View and the ViewModel whereas Angular has some other stuff that you could simply ignore.

I agree that there are differences, but they are all part of the same family. In fact, view models dates back to the four component MVC patterns once used in Smalltalk (having a application model not to be confused with the domain model). The MVVM variant adds automatic two way binding. This is the case with these four great implementations.

My view is this:

Angular.
Pros: Fast. Elegant and simple to use. 
Cons: Has irrelevant stuff dealing with non MVVM/MDV concepts that hides the nice MVVM/MDV functionality

Google MDV
Pros: Elegant and simple to use.
Cons: Just a proof of concept. Unstable. Buggy. Super slow.

Knockout
Pros: Stable, Complete
Cons: Slow. Needs wrapper functions (rather than JSON tree proxies).

JsView
Pros: Decent performance, associated with jQuery
Cons: Not beta yet. Not that elegant.

[LessX]

I tested the new Kendo UI Q1'12 Beta MVVM FEATURE and I only have two words for this:

just beautiful!!

I did not expect less than kendoUI development team.

very good work guys.

[Vesselin Obreshkov]

(please delete me)