As I have already stated in this thread, we are currently working on the "Unbound Mode" of the pager. Here it is again:
When the pager is in Unbound Mode, i.e. it has no Source defined, you will be able to manually specify the total item count so that the pager can calculate its number of pages. The pager will be fully functional with the only difference that it has no source collection to page. This will allow the developer to use the exiting UI without any efforts. The developer can attach to the PageIndexChanging and PageIndexChanged events of RadDataPager and perfom any kind of action depending on the requirements.
So, you will set the total amount of records (once the feature is ready). Then each time a PageIndexChanged event occurs -- you will pull only this page from your web service.
To avoid any further confusion: There is no endless type
or mode or whatsoever. This is just an online example.
demonstrates a possible
implementation of IPagedCollectionView.
This is is not a feature of the pager. It is just a dummy example. And if you take a closer look at the example -- there absolutely no data. Everything is fake. So long story short -- there is not such thing as endless mode. The pager can either have a real Source or be Unbound (once the feature is ready). When it is Unbound -- you tell it how many pages to display in the UI and then you handle its events and do whatever you like in the event handlers.
I hope this makes sense.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items