Thread panel and forum composer: build ComposerOptions from composer_context (timeout barrier) #602

Open
opened 2026-11-15 06:38:36 +00:00 by charles · 0 comments
Owner

Follow-up of #528 (PR #592, review round 1).

crates/fluxer-ui/src/screens/main/threads/panel.rs and the forum composer still build their own ComposerOptions, so the composer barriers of spec §3.9 (the timeout bar with its M:SS countdown in particular) do not replace the thread panel's composer, and its placeholder/disabled state does not come from the core's composer_context. These files were outside Task 37b's list. Use barrier::model / composer_context there as screens/main/messages.rs does, and extend the shell's countdown timer (app.rs, barrier::countdown) to the open thread panel's channel.

Seen on branch dailyuse-37b-ui-composer-barriers-blocked at 8f48edb.

Follow-up of #528 (PR #592, review round 1). `crates/fluxer-ui/src/screens/main/threads/panel.rs` and the forum composer still build their own `ComposerOptions`, so the composer barriers of spec §3.9 (the timeout bar with its M:SS countdown in particular) do not replace the thread panel's composer, and its placeholder/disabled state does not come from the core's `composer_context`. These files were outside Task 37b's list. Use `barrier::model` / `composer_context` there as `screens/main/messages.rs` does, and extend the shell's countdown timer (`app.rs`, `barrier::countdown`) to the open thread panel's channel. Seen on branch `dailyuse-37b-ui-composer-barriers-blocked` at 8f48edb.
charles added this to the Daily use milestone 2026-11-15 06:38:36 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
charles/fluxer-native#602
No description provided.