This question is locked. New answers and comments are not allowed.
Are we going to see "LINQ-based Telerik data engine" in SL for the first version?
Is this engine going to utilize "ADO.Net Data Services client" to talk to the Data Service?
Secondly, when do you think we can see the Carousel control in SL? Next beta perhaps?
Thanks!
..Ben
Is this engine going to utilize "ADO.Net Data Services client" to talk to the Data Service?
Secondly, when do you think we can see the Carousel control in SL? Next beta perhaps?
Thanks!
..Ben
3 Answers, 1 is accepted
0
Hello Ben,
Yes, we will be porting our LINQ-based data engine to SL as the grid depends on it :-). The engine uses LINQ to objects, and we have no plans on coupling it to ADO.NET Data Services. Maybe we can provide some way to plug data services or something like that -- can you expand a bit on the usage scenario you are after?
As far as the Carousel control port for SL is concerned, we do not have a timeframe yet. The focus will be mainly on the grid control, and we plan to turn our attention to the carousel once the grid is running smoothly on SL.
All the best,
Hristo Deshev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Yes, we will be porting our LINQ-based data engine to SL as the grid depends on it :-). The engine uses LINQ to objects, and we have no plans on coupling it to ADO.NET Data Services. Maybe we can provide some way to plug data services or something like that -- can you expand a bit on the usage scenario you are after?
As far as the Carousel control port for SL is concerned, we do not have a timeframe yet. The focus will be mainly on the grid control, and we plan to turn our attention to the carousel once the grid is running smoothly on SL.
All the best,
Hristo Deshev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Ben Hayat
Top achievements
Rank 2
Rank 2
answered on 22 Aug 2008, 01:13 PM
Hi Hristo (Deshev);
>>The engine uses LINQ to objects, and we have no plans on coupling it to ADO.NET Data Services. Maybe we can provide some way to plug data services or something like that -- can you expand a bit on the usage scenario you are after?<<
If you go back to the original question, you'll notice one key point in my question which was the word "Client" of ADO.Net Data Services. I don't expect you to write the client side to Astoria (that's what MSFT is working on now - which basically handles all the communication, tracking and etc to get the data to SL side). But once that data (or I should say objects) have been de-serialized and are available at the SL client side (which are going to be in the form of IQuerable list) for the client LINQ to use it. Up to this much will be provided by MSFT. My question was, will your engine then connect to this set of data that is provide by the client side Astoria? And if yes, what functionality will this engine provide?
Thanks!
..Ben
Also, thanks for the road map on the carousel component
>>The engine uses LINQ to objects, and we have no plans on coupling it to ADO.NET Data Services. Maybe we can provide some way to plug data services or something like that -- can you expand a bit on the usage scenario you are after?<<
If you go back to the original question, you'll notice one key point in my question which was the word "Client" of ADO.Net Data Services. I don't expect you to write the client side to Astoria (that's what MSFT is working on now - which basically handles all the communication, tracking and etc to get the data to SL side). But once that data (or I should say objects) have been de-serialized and are available at the SL client side (which are going to be in the form of IQuerable list) for the client LINQ to use it. Up to this much will be provided by MSFT. My question was, will your engine then connect to this set of data that is provide by the client side Astoria? And if yes, what functionality will this engine provide?
Thanks!
..Ben
Also, thanks for the road map on the carousel component
0
Accepted
Hello Ben,
Yes, most certainly we will be supporting all Astoria objects that have been passed to the data engine. At the moment we plan to make sure that we support the deserialized objects and work with those just as with any other .NET object. Taking care of advanced features, if we need to support any, will come later.
All the best,
Hristo Deshev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Yes, most certainly we will be supporting all Astoria objects that have been passed to the data engine. At the moment we plan to make sure that we support the deserialized objects and work with those just as with any other .NET object. Taking care of advanced features, if we need to support any, will come later.
All the best,
Hristo Deshev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.