[Solved] Any info on the new Data binding engine?

[Ben Hayat]

Hi Team;

I have not installed the Q2 yet, since I'm waiting for Q2 for SL3 version. However, I was reading on "What's new" page and it references about the new Data Bindin Engine. Can you point me to where I can read and learn more about this?

Thanks!

[Stefan Dobrev]

Hello Ben,

Our new data engine is based around the QueryableCollectionView we have introduced in Q2. This new collection view is entirely based on LINQ and knows how to push all data operations (sort, filter, group, page and aggregate) back to the query provider it is bind to.

To see this in action you can check this WPF example locally. Unfortunately currently there is now full blown query provider implementation for Silverlight and the new data engine cannot shine brightly there yet.

What you must know about QueryableCollectionView is that (similar to RIA Services DomainDataSource model) it uses the "Descriptor" nomenclature instead of the "Description" one. This means that you must add Filter/Sort/Group Descriptor to the collection in order to perform your data operations on the server.

Feel free to play with it and send us your feedback.

Have fun,
Stefan Dobrev
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

[Ben Hayat]

Thanks Stefan;

So, is this new engine a substitude for RIA ObjectDataSource?

If someone is using RIA ObjectDataSource in SL3, how will your engine and ODS work with your grid?

Thanks!

[Stefan Dobrev]

"So, is this new engine a substitude for RIA ObjectDataSource?" - no it will play nicely with DomainDataSource. Expect similar blog post to this one, when we the next CTP of RIA Services is publicly available.

Stefan Dobrev
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

[Ben Hayat]

Thanks Stefan for confirmed answer. Looking forward to your blog.

One other question that you may want to include some info in your blog. Currently, since the ODS is closely connected to UI, it's not meant to be used a pattern like Prism & MVVM to break things up. How would your engine play in this scenario? Can this engine be used in the ModelView layer for data accessing?

Thanks again for clearing up these questions!

[Stefan Dobrev]

Hi Ben,

The data engine definitely can serve as a good ViewModel abstraction for the grid. Expect some blog posts in the near future.

Best wishes,
Stefan Dobrev
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.