[PATCH 4 of 4] hgweb: render next pages on /graph incrementally

[Anton Shestakov]

On Thu, 14 Dec 2017 21:11:35 +0900
Yuya Nishihara <yuya at tcha.org> wrote:

> On Wed, 13 Dec 2017 00:27:49 +0800, Anton Shestakov wrote:
> > # HG changeset patch
> > # User Anton Shestakov <av6 at dwimlabs.net>
> > # Date 1512978236 -28800
> > #      Mon Dec 11 15:43:56 2017 +0800
> > # Node ID 865e71e7184410b60e2dd2912407d3884514e437
> > # Parent  79649cbad159b574d85902abc195089af01241cf
> > hgweb: render next pages on /graph incrementally
> > 
> > Previously, when user scrolled down to see the next page on /graph, all hgweb
> > did was re-render everything that would be visible (by simply incrementing
> > revcount). It was not efficient at all, and this patch makes /graph page behave
> > similarly to the regular /log: every new page only consists of new changesets,
> > no duplication, and only jsdata is based on the full set of changesets required
> > to build accurate graph.
> > 
> > This is achieved by adding "?graphtop=<node>" to the next page URL template,
> > effectively remembering where the graph started, and using that value to create
> > the new `tree` that covers the whole visible graph. That variable is then used
> > to produce jsdata for redrawing graph client-side.
> 
> Can you update the docstring of graph()?

Right, I'll send a follow-up soon. Thanks for reviewing!