| Comment: | docs: page the documentation index
Wiki pages alone did not need paging — human authorship bounds them at a couple of hundred — but the tree half is unbounded, and the old 400 cap was a dead end with everything past it reachable only by guessing a filter. Pages of 100, since these are one-line rows in two columns. One function builds every link, so a filter, a sort, a page and the associated-wiki choice cannot lose each other; a stale offset lands on the first page rather than an empty one. The pager type is shared with the tracker now, which is what it always was. |
|---|---|
| Timelines: | family | ancestors | descendants | both | docs-paging |
| Files: | files | file ages | folders |
| SHA3-256: |
fa70fc4958db90822a772cbc2803df35 |
| User & Date: | dmestas on 2026-08-23 01:41:12.665 |
| Other Links: | branch diff | manifest | tags |
|
2026-08-23
| ||
| 01:44 | docs: page the documentation index (merged with the structure panel) closed check-in: 430e076558 user: dmestas tags: docs-paging-merge | |
| 01:41 |
docs: page the documentation index
Wiki pages alone did not need paging — human authorship bounds them at a couple of hundred — but the tree half is unbounded, and the old 400 cap was a dead end with everything past it reachable only by guessing a filter. Pages of 100, since these are one-line rows in two columns. One function builds every link, so a filter, a sort, a page and the associated-wiki choice cannot lose each other; a stale offset lands on the first page rather than an empty one. The pager type is shared with the tracker now, which is what it always was. closed check-in: fa70fc4958 user: dmestas tags: docs-paging | |
| 01:29 | merge docs-tab: one documentation index for the wiki and the tree check-in: 4629420231 user: dmestas tags: trunk | |