Hi!
After reading this blog post, I came a little nervous of the future of Kendo MVVM and templating. We have some applications that are built around this functionality. Can we trust that the functionality will stay with Kendo in the future so we can use it on larger projects too? I think it is nice to have all the functionality via Kendo and no need for overhead of third party libraries and integrating them.
I hope I will get some answers directly from Telerik too - thanks!
3 Answers, 1 is accepted
0
Hello,
the link to the blog post is empty.
Regards,
Petyo
Telerik
the link to the blog post is empty.
Regards,
Petyo
Telerik
Get started with Kendo UI in days. Online training courses help you quickly implement components into your apps.
0
Tero
Top achievements
Rank 1
Rank 1
answered on 17 Jun 2016, 11:15 AM
http://developer.telerik.com/featured/what-to-expect-from-javascript-in-2016-frameworks/
0
Accepted
Hi Tero!
My name is Burke, and I'm the one who researched and wrote that post. I think maybe the part about the MVVM is a bit misleading, and that's my fault.
Kendo UI MVVM in it's current incarnation will be supported and developed further. Nothing will change there. I was referring to integrations like Angular 2 and React. Within the context of these frameworks, the Kendo UI MVVM is redundant or necessary, so there is no point in us providing another binding framework when the framework within which Kendo UI is used already contains all of this functionality.
I hope this helps clarify your question. Our vanilla MVVM isn't going anywhere since all of Kendo UI depends on it very heavily.
Feel free to contact me directly if you have any further questions: burke.holland@telerik.com.
Cheers!
Burke
Telerik
My name is Burke, and I'm the one who researched and wrote that post. I think maybe the part about the MVVM is a bit misleading, and that's my fault.
Kendo UI MVVM in it's current incarnation will be supported and developed further. Nothing will change there. I was referring to integrations like Angular 2 and React. Within the context of these frameworks, the Kendo UI MVVM is redundant or necessary, so there is no point in us providing another binding framework when the framework within which Kendo UI is used already contains all of this functionality.
I hope this helps clarify your question. Our vanilla MVVM isn't going anywhere since all of Kendo UI depends on it very heavily.
Feel free to contact me directly if you have any further questions: burke.holland@telerik.com.
Cheers!
Burke
Telerik
Get started with Kendo UI in days. Online training courses help you quickly implement components into your apps.