Grid: Paging of JavaScript Array already in memory

[Preston]

Hello,

i want to page the contents of a Java Script array with 50 rows (no server side paging here) directly on the client, showing the array in pages of 15 entries.

My problem now is, that the grid always shows all of the 50 objects within the Data.Store, although i defined:
ds.load({params:{start:0, limit:15}});

I use a regular ArrayReader and a MemoryProxy.

Funny thing is, the footer displays the correct number of entries in the array and the page numbers are also correct. But unfortunately i can´t skip through the in memory data.

Can anybody help me here?
What do I have to do, to enable Client Side paging?

The relevant code i currently use for this:

    var ds = new Ext.data.Store({               
                            proxy: new Ext.data.MemoryProxy(myJavaScriptArray),
                          reader: new Ext.data.ArrayReader(
                          {totalProperty: 50',
                           id: 0},
                           […
//some more code here
                              ...     ]

        grid.render();     
       
        var gridFoot = grid.getView().getFooterPanel(true);

        // add a paging toolbar to the grid's footer
        var paging = new Ext.PagingToolbar(gridFoot, ds, {
            pageSize: 15,
            displayInfo: true,
            displayMsg: 'Displaying topics {0} - {1} of {2}',
            emptyMsg: "No topics to display"
        });         
       
        // trigger the data store load
        ds.load({params:{start:0, limit:15}});

[BernardChhun]

correct me if I'm wrong but the grid is using remote paging with the HttpProxy only.

I'm not a 100% sure about this but local paging isn't working.

[Preston]

Thanks for the answer.

Can anybody confirm, that local paging is not supported? I mean it´s almost working as far as the footer navigation goes.

And, if local paging is not supported, can one give me a hint on how to implement this? I mean, the data is already in the proxy and the reader would have to skip through the array somehow...

[KimH]

Local paging is NOT supported.... but my guess is that it will be in an upcomming release/revision as this question has been asked several times now...

[Animal]

I don't understand why you'd want it. Given that the data is there in the page, surely it's more convenient and intuitive to use the scrollbar for the purpose for which it was provided?

[Preston]

Yeah, I agree with you Animal. However my table has LOTS of columns (e.g.25) and when stuffing in 1000 rows all at once the rendering takes a lot of time. So paging with 50 or so shown on one page is my only way out of this misery.

I have no possibility of paging the data sets through another server round-trip, because it is not possible within my application architecture (as strange as this sounds).

[mdissel]

Another reason to support "in-memory-paging" is to make it possible to load the first page of the grid during the initial loading of the page, instead of running an extra ajax call after the page has been loaded.


Thanks

Marco

[JeffHowden]

Another reason to support "in-memory-paging" is to make it possible to load the first page of the grid during the initial loading of the page, instead of running an extra ajax call after the page has been loaded.

That'd be more complicated as you'd need to switch from a memory proxy to an http proxy for subsequent calls.

[cyberlot]

That'd be more complicated as you'd need to switch from a memory proxy to an http proxy for subsequent calls.

Just want to get some sort of verification, Will local paging be supported at some point???

Local paging would be great for reducing server load.

[Animal]

Well, it will move the server load.

The extraction of the whole dataset from the database, and the downloading of the data into the browser happen up front before the page is rendered, rather than on demand, and only if the user decides to view more pages.