I've been looking at Angular Kendo and am wondering what kind of benefit or need beyond Kendo's MVVM implementation that Angular serves.
I've reviewed all the documents on labs.kendoui.com and haven't found anything that clearly details what drove the decision... which could be very important information for architect types that are trying to put together a stack for a web-based application.
Was this a case of using AngularJS to see if you could... or?
I've reviewed all the documents on labs.kendoui.com and haven't found anything that clearly details what drove the decision... which could be very important information for architect types that are trying to put together a stack for a web-based application.
Was this a case of using AngularJS to see if you could... or?
1 Answer, 1 is accepted
0
Accepted
Hi Rick,
Good question. There is indeed a lot of overlapping functionality, which both Kendo and Angular provide but in different ways. If you already use Kendo but not Angular, my suggestion is to continue to do so, and you don't need the Angular-Kendo bindings.
FYI, we currently support Angular 1.x, but Angular 2.0 is in the works and it looks like it won't be a simple drop-in replacement (different API, written in EcmaScript 6). That's something we don't do at Kendo -- our motto is "no breaking changes!" (except perhaps with very good justification).
The bindings were created for Angular users -- that is, the goal was to provide a UI toolkit for people who already use Angular but perhaps not using Kendo. By creating Angular directives for Kendo widgets we provide a familiar API and behavior for Angular users.
Regards,
Mihai
Telerik
Good question. There is indeed a lot of overlapping functionality, which both Kendo and Angular provide but in different ways. If you already use Kendo but not Angular, my suggestion is to continue to do so, and you don't need the Angular-Kendo bindings.
FYI, we currently support Angular 1.x, but Angular 2.0 is in the works and it looks like it won't be a simple drop-in replacement (different API, written in EcmaScript 6). That's something we don't do at Kendo -- our motto is "no breaking changes!" (except perhaps with very good justification).
The bindings were created for Angular users -- that is, the goal was to provide a UI toolkit for people who already use Angular but perhaps not using Kendo. By creating Angular directives for Kendo widgets we provide a familiar API and behavior for Angular users.
Regards,
Mihai
Telerik
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!