diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/next-daemon.md | 39 |
1 files changed, 33 insertions, 6 deletions
diff --git a/docs/next-daemon.md b/docs/next-daemon.md index 95713b42..0462c445 100644 --- a/docs/next-daemon.md +++ b/docs/next-daemon.md @@ -403,7 +403,9 @@ the ponytail lens: named in a path yet (a script's focus or layout is that view's). - Every change draws every view (`needs_frame` is the session's); a view's own dirtiness waits for a measurement that wants it. - - Dump, Restore and Handover keep one view, the live one. + - Restore and `-l` keep one view, the live one; a dump has every view + (phase 2 notes), and Handover carries panes, which join the views of + the window they land in. - **What proved wrong in the design.** "Views" in the design were a struct the core reads through; the swap made them cheaper and kept every reference. Its rollback copy (phase 5) is the same list of fields. The @@ -1340,14 +1342,39 @@ dump hooks; `pardes-snap --dump`, `pardes-monkey --dump`, and both in layout (`dropMissing`), never more. What was let go is the session's first message after the load. A pane whose terminal another build could not read is a fresh terminal (`ensureKind`). -- **Roots, not wrappers.** A session's dump is three roots: the core, +- **Roots, not wrappers.** A session's dump is five roots: the core, read *into* a core `Pardes.create` made (its local, derived and authority fields stay create's: no defaults to invent for an arena or a host), its 9P mounts (state the user made, inside the 9P server's - authority `fs`), and which file panes' files were on disk when it was - made (one gone by the load is said deleted, so Del asks: its text is - nowhere else; one never on disk comes back as it was). A pane's dump - (the store's, a handover's) is a Pane alone. + authority `fs`), which file panes' files were on disk when it was made + (one gone by the load is said deleted, so Del asks: its text is nowhere + else; one never on disk comes back as it was), the theme's name, and + the views not live. A pane's dump (the store's, a handover's) is a Pane + alone. +- **Every view is in the dump** (decided after phase 4 merged). The live + view is the core's own fields, so `view` and `views_open` were dumped + already, and a session dumped with several views loaded into a core + that said so with no parked slot: its first view switch, close or + drawing of the others unwrapped a null. Leaving them out would have + needed `load` to fold them anyway, and the join (phase 5) needs them: + a replica applies the other clients' `toView`. So `views.dumped` writes + each open view but the live one (the live one's slot is stale by + design): its share of the session but what drawing keeps + (`Pardes.replica.local`, computed from `views.fields`: its panels as + presented, its animations), its slots' serials, and its share of every + pane (`pv_known` says which shares own their selections, not which + exist: a parked view has one of every pane). `views.undumped` parks + them again in `load`, last, so nothing after it rolls back what it + moved; a pane a view has no share of gets the live view's, a view the + core says open that the dump lacks is closed, a dump with no views root + (before this) has one view. They stay out of the digest as before + (parked views are checked when live again); the gate is the re-dump + byte for byte, now also on the three-view monkey seeds. A session + *revived* for one client (Restore, `-l`) is one view, the live one as + view 0 (`views.only`, what the hosts already assumed), and a pane + carried or reopened takes the view it lands in (`sized_by`, + `prompt_view`). Cost: the views root is empty for one view; with + several, a share is about 100 bytes a pane a view. - **Aliasing by reference.** Zerox twins share their text and undo again, an `inherited` cwd points at its pane again. Keyed by address, length and type, which is also what made twins dump their text once. |
