Thank you for giving the Kendo UI ListView a test run.
The data source data
of any data-bound widget goes through observable wrapping which is underpinned by the Kendo UI MVVM framework
. Every item in the data source has the highlighted added to it :
For the change event of the MVVM framework to be triggered, the set()
method of the Observable Object
should be used.
are bound with the "data-bind=value:someproperty" Kendo MVVM attributes
. In effect, they perform the call to the set() method for you and the CRUD operation is triggered so a request is made to the server out of the box as long as the Actions are configured.
.DataSource(dataSource => dataSource
.Model(model => model.Id(
.Create(create => create.Action(
.Read(read => read.Action(
.Update(update => update.Action(
.Destroy(destroy => destroy.Action(
So finally, to answer your question regarding the ObservableCollection, I suppose you could use it on the server when the change from the client is transmitted to the server. However, we do not yet have such example and if it is necessary, I would need some time to get it to you.
I hope the explanations above will give you a better idea. Let me know if there is anything else that I should delve into.