-
28 May 2010 12:05 AM #121
RESPECT for this very nice plugin! Great work Condor!
regards
p3p3
-
29 May 2010 6:11 AM #122Sencha - Community Support Team
- Join Date
- Mar 2007
- Location
- The Netherlands
- Posts
- 24,251
- Vote Rating
- 41
OK, I created an Ext 3.2 compatible PagingStore.
New features in v0.5:
- Only for Ext 3.2 (and up?).
- Added PagingGroupingStore (although I don't recommend using it).
- Added Ext.ux.PagingStore with doRefresh patch and support for adding/removing/clearing records.
-
2 Jun 2010 8:51 PM #123
Hi Condor
I know you don't recommend using your great plugin with a GroupingGrid. However, is it possible in case if let say group C spans across 2 pages, recalculate a page size after load and apply paging again with a new page size to avoid the spanning?
Thank you
-
2 Jun 2010 10:58 PM #124Sencha - Community Support Team
- Join Date
- Mar 2007
- Location
- The Netherlands
- Posts
- 24,251
- Vote Rating
- 41
Yes, you could do that.
For initial load I recommend using suspendEvents/resumeEvents to stop it from displaying the page with the wrong pageSize.
-
2 Jun 2010 11:48 PM #125
V0.5 START and LIMIT params
V0.5 START and LIMIT params
Hi Condor,
Thanks for your great work on this UX. It works and performs great even with large record sets (5000+)!
Yesterday I moved a project to Ext 3.2.1 and also upgraded the PagingStore to the new 0.5 version. I then noticed a behaviour which caused a problem for me:
In version 0.5 the START and LIMIT params are also being send to the server when retrieving records, version 0.41 did not have this behaviour.
Is this intentional and what is in your opinion the best way to prevent this without have to do 'server side' adjustments?
I suppose replacing:
with:PHP Code:this.proxy.request(Ext.data.Api.actions[action], rs, options.params, this.reader, this.createCallback(action, rs, batch), this, options);
Does fix this for me. However this is not really a 'correct' fix.PHP Code:this.proxy.request(Ext.data.Api.actions[action], rs, this.baseParams, this.reader, this.createCallback(action, rs, batch), this, options);
What are your thoughts on this?
Many thanks for this UX and your help is very much appreciated!
-
3 Jun 2010 5:46 PM #126
Thanks Condor
But if I suspendEvents on beforeload or on load, how I can check if group C spans across 2 pages? I will not be able to use for example store.collect('groupfield') to get unique fieldname and compare the set per page. Is there any better solution how can I check if group C spans accross 2 pages, and if yes, get a number of records grouped by group C and recalculate a paze size by adding this number to the initial page size and reload the store?
A simple example will be really usefull.
Thank you in advance
-
4 Jun 2010 3:33 AM #127
how to place a date field on toolbar..please help with code..i want that date to be inserted into the grid
-
4 Jun 2010 3:46 AM #128Sencha - Community Support Team
- Join Date
- Mar 2007
- Location
- The Netherlands
- Posts
- 24,251
- Vote Rating
- 41
Completely untested:
Code:store.suspendEvents(); store.load({ callback: function(){ var limit = ... // calculate limit for first page based on first group store.resumeEvents(); store.load({params: {start: 0, limit: limit}}); } });
-
4 Jun 2010 3:47 AM #129
-
5 Jun 2010 12:13 PM #130
Hi!
I'm using PagingGroupingStore in a grid and everything is fine with that, but the sort options of the grid don't work :\
Is it normal this conflict?


Reply With Quote