5 Answers, 1 is accepted
Currently loading events on scrolling (infinite scrolling or virtualization) the Scheduler's view is not implemented. This feature has been requested before: see this feature request in our Feedback Portal. At present it is not yet approved for implementation by the team so we would suggest voting for it. The highly demanded requests are usually planned with precedence for subsequent releases.
Binding to the response cannot be made faster, and most probably the rendering is what causes the slow down in your case. You could verify this by hiding the Scheduler with CSS initially:
and showing it when it is bound to the data, in its dataBound event handler:
I did manage to work a way around this slowness issue on render.
I have implemented a resource pagination through which only a small portion of large data set is displayed making the widget very fast in rendering.
PS: This is just my concept may have some bugs
I am glad you have found a custom solution that avoids loading all resources at once. Thank you for sharing it. I hope it will be useful to other members of the community who face a similar scenario.