You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of rendering page by page, for a fixed state of filtering, sorting, sampling, and panel layout, start to build a cache of hidden divs containing each page's rendered content.
Thus when the user clicks next, if the next page has been pre-cached, it will simply load quickly, otherwise, it will trigger the output to be rendered the usual way. Users typically stop to study the current page for a small amount of time, so it would be good to remove the page changing latency by rendering it while they are viewing.
I think the best way to do this is by a specially-numbered div for each page and a special shiny output that keeps triggering more data to be sent as it keeps rendering.
The text was updated successfully, but these errors were encountered:
Instead of rendering page by page, for a fixed state of filtering, sorting, sampling, and panel layout, start to build a cache of hidden divs containing each page's rendered content.
Thus when the user clicks next, if the next page has been pre-cached, it will simply load quickly, otherwise, it will trigger the output to be rendered the usual way. Users typically stop to study the current page for a small amount of time, so it would be good to remove the page changing latency by rendering it while they are viewing.
I think the best way to do this is by a specially-numbered div for each page and a special shiny output that keeps triggering more data to be sent as it keeps rendering.
The text was updated successfully, but these errors were encountered: