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
{{ message }}
This repository was archived by the owner on Aug 9, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 9, 2024. It is now read-only.
GridPanel data remote paging and sorting support #1843
GridPanel paging and sorting historically been aided by helpers in Ext.NET 5. In particular the Ext.Net.Paging<T> type in Ext.NET 5- employs the required interface for response to such requests. This can be seen in these examples:
Another approach is using Ext.NET's own Page Proxy, and implementation both client-side and server-side thought to improve the communication of the remote pages. This component extends Ext.data.proxy.Server.
Its main use is to provide the correct values through client-server communication like in
Notice the sort member is a string of a nested json.
As for the response, it usually involves an object with two members: one containing the data itself for the specific page, and another for the total count, which would allow the pager to know how many pages it should be informed to page switching toolbar. In practice,
"data": [{(dataentrieshere)}],"total": 50000
The data and total fields being configurable, respectively, via the reader's RootProperty and TotalProperty, respectively.
When the directFn (using direct methods to fetch pages) is employed, the returned value can be either a generic object with a List and an integer, the Paging<T>with Data and TotalRecords filled, or an anonymous new { data = List<T>(), total = integer }. There is also the StoreRequestParameters class to make it easy to map the parameters from the specified Dictionary<string, object> extra parameters (see the related example for more details).
All examples on WebForms Examples Explorer using the feature:
Activity