Tickets :: [#2584] Pagination

6.0.0-beta1

7/19/25

Summary	Pagination
Queue	Chora
Queue Version	HEAD
Type	Enhancement
State	Resolved
Priority	1. Low
Owners
Requester	techtonik (at) php (dot) net
Created	09/10/2005 (7252 days ago)
Due
Updated	03/15/2006 (7066 days ago)
Assigned
Resolved	03/15/2006 (7066 days ago)
Milestone
Patch	No

03/15/2006 07:05:58 AM	Chuck Hagenbuch	Comment #5 State ⇒ Resolved	Reply to this comment
What I've done is restrict the default revision log view to the latest 100 revisions. Lets modem uses avoid getting sucked in for basic usage, and can go make a cup of coffee if they have to see the whole thing. Cool?

03/05/2006 12:21:30 PM	Jan Schneider	Comment #4	Reply to this comment
No matter how good our caching is, the page size is a problem. Take the changelog of files like IMP's compose.php or message.php. They are almost impossible to view over a modem line.

03/05/2006 02:04:20 AM	Chuck Hagenbuch	Comment #3 State ⇒ Feedback	Reply to this comment
I'm still not convinced that paging is the solution here. Jan, I'm guessing from your summary/state change that you do, can you say why?

11/28/2005 03:58:22 PM	Jan Schneider	Summary ⇒ Pagination State ⇒ Accepted

09/11/2005 04:09:37 AM	Chuck Hagenbuch	Comment #2 State ⇒ Feedback	Reply to this comment
There isn't a single table that spans the whole page, so while cutting down the size of the HTML in general would be useful, I'm not sure that will greatly speed display. Pagination would be one option, and better caching is another...

09/10/2005 07:10:42 AM	techtonik (at) php (dot) net	Comment #1 Priority ⇒ 1. Low Type ⇒ Enhancement Summary ⇒ Pagination / remove page table Queue ⇒ Chora State ⇒ New	Reply to this comment
While viewing file with long commit history (> 100 commits) you have to wait a lot of time before whole log table loads and it takes a lot of traffic on each page reload. If it will be possible to display entries or groups of entries separately in <div> or add pagination ability - the interface will be more user friendly.