Host floating chats on the shell window system
Phase 2.3 and 2.4 of docs/plans/floating-windows.md. A floating chat is a window of the chat kind over the app's WindowManager, built from the app-lifetime ChatRuntime, so it shows over every destination and at start without the Chat destination being built. Float and Dock move the same keyed view between the tiling and the window host. The pipelines app keeps one runtime and one ChatWindows; saved chatFloat records (v1 and v2) are brought over once. ChatFloatHost, ChatFloatWindow, the float frames and binding, the controller's float list and FloatingFocusRoot are gone; the workspace only asks whether a chat is out in a window. Every MenuAnchor targets the root overlay (guarded by a test), and menus and tooltips name the Alt chords.
This commit is contained in:
@@ -5,11 +5,11 @@ system; no feature uses it yet (chats move in Phase 2, the terminal in Phase 3).
|
||||
|
||||
## Pieces (`lib/shell/windows/`)
|
||||
|
||||
- `WindowManager` (`AppWindows.manager`): the open windows bottom to top, frames,
|
||||
- `WindowManager` (one per `PipelinesApp`): the open windows bottom to top, frames,
|
||||
minimised/maximised, group show/hide, cycling. Saved through `WindowStore`
|
||||
(`pipelines.windows.v1`), one record for every server; server-scoped windows
|
||||
carry their server key and only the current server's are listed.
|
||||
- `WindowKind` (`AppWindows.kinds`): what a kind of window builds, its title,
|
||||
- `WindowKind` (registered on the manager's `kinds`): what a kind of window builds, its title,
|
||||
icon, title-bar actions, minimum size and saved data.
|
||||
- `WindowHost`: the windows as plain children of the terminal stage's stack, in
|
||||
the shell page (not an overlay above it), outside every destination.
|
||||
|
||||
Reference in New Issue
Block a user