Repository navigation
Conversation
Chore: Bump the version to 0.0.4
…ition The owner asked for several windows in one process, with an IDE tab torn off into its own window the way Electron apps do it (2026-10-26). D23 records the shape proposed for it and what was rejected: a Host per window, a process per window, an imperative open_window, and moving nodes between windows. Refs #355
Window becomes a widget at the root: inserting one opens a platform window, removing it closes it. All windows share one Host, one composition and one node table, so shared state needs no new mechanism and the boundary functions stay as they are (PR-2); only the schema changes (FR-7). Single window apps are unchanged in source and in bytes. Covers per-window title, size, position, chrome, icon, zoom and theme override; close requests, focus, moves; window ids on the existing window events; the last window policy (macOS keeps running); tab tear-off with DragFromPointer and drop targets; platform scope with reasons for iPadOS, Android, Web and the GraalVM path; CI-testable acceptance criteria. Refs #355
The owner put mobile in scope the same day: "compose-rust에 여러 창 띄우기 할 때 모바일도 해줘야해. 안드로이드는 액티비티 하나 더 추가하는걸로 생각하면 되겠지?" A window is an Activity on Android and a UIScene on iOS and iPadOS, behind the same Rust API. Records the cost: system-created windows need a stable RestoreKey, and the Android Host lives as long as the process. Refs #355
Android: one window is one Activity in the same process and Host, launched with NEW_DOCUMENT | MULTIPLE_TASK (and LAUNCH_ADJACENT), so each shows separately in split screen, freeform, desktop windowing and recents. Recreation keeps the window's node and state. iOS and iPadOS: one window is one UIScene; on iPhone opening a window switches to the new scene; scene disconnect keeps the node and reconnect redraws it. Tear-off is one TearOffKey property everywhere: NSUserActivity on iPadOS, ClipData with a launch PendingIntent on Android 12L+, a menu action where the system has no drag, and DragFromPointer on desktop. RestoreKey and WindowRequested match windows the system creates or restores. Adds emulator and simulator acceptance criteria; Web and the GraalVM path stay not applicable. Refs #355
The owner approved the design on 2026-10-26: Window nodes, one Host shared by every window, single window apps unchanged, TearOffKey on all platforms. Refs #355
Docs: Add FR-53 and D23, several windows in one process with tab tear-off
# Conflicts: # docs/INTENT.md # docs/SPEC.md
Docs: Screen previews and PNG export (D24, FR-54)
…st the chat pattern (NFR-17, #362)
Fix: Stop the attribute buffer pool growing by one buffer per node update
…eptance criteria (#364)
This was referenced Nov 7, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Step 3 of #364. INTENT D23 records the owner's decision (2026-10-26, quotes included), the private API risk and the fallback rule. SPEC FR-19.8 gets criterion 5, an opt-in mode with its acceptance criteria and the CI numbers from the probe (PR #365). Stacked on #354 like #365. Items 3 to 5 of the criteria stay marked unmeasured until the renderer PR and the owner's run.