Our Views are composed from dynamic components, each having own "View" and ViewModel. They are built independently and can have identical names of bound properties in a Model. As far as I see, when applying binding between View and ViewModel, Kendo UI will travers entire DOM tree. This will apply wrong values to components that do not belong to the "View" in question, but have the same name of bound properties. With Knockout I can use "controlsDescendantBindings" instruction to stop binding from drilling down on a DOM subtree - does Kendo UI have any way to do the same?
Thanks,
Sam
1 Answer, 1 is accepted
0
Accepted
Hello Sam,
I am afraid the Kendo UI MVVM binding does not provide a mean to control which parts of the View to be bound. My advice is to split the application into multiple Views, each in separate container and bind them to their respective ViewModel.
Regards,
Alexander Popov
Telerik
I am afraid the Kendo UI MVVM binding does not provide a mean to control which parts of the View to be bound. My advice is to split the application into multiple Views, each in separate container and bind them to their respective ViewModel.
Regards,
Alexander Popov
Telerik
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!