Pagination

While viewing file with long commit history (> 100 commits)

Sat, 10 Sep 2005 03:10:42 -0400

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

or add pagination ability - the interface will be more user friendly.

There isn't a single table that spans the whole page, so whi

Sun, 11 Sep 2005 00:09:37 -0400

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...

I'm still not convinced that paging is the solution here. Ja

Sat, 04 Mar 2006 21:04:20 -0500

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?

No matter how good our caching is, the page size is a prob

Sun, 05 Mar 2006 07:21:30 -0500

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.

What I've done is restrict the default revision log view to

Wed, 15 Mar 2006 02:05:58 -0500

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?