WEFT_OS/examples/org.weft.demo.notes
Marco Allegretti ddd79f6ab1
fix(appd): keep a session running while it answers a close, and add a forced stop
An application with the ask close policy could decline every close, and
nothing could end it. TERMINATE_APP now takes force, which terminates
the session without asking. The taskbar offers it as Force quit once an
app has had longer than the close timeout to answer.

The close interaction now comes before Running -> Stopping, as blueprint
6.2 requires. The session stays running while the application answers,
and a declined close no longer moves Stopping back to Running. Stop
requests reach the supervisor on a channel, so a repeated or forced
request during the close wait is seen without registering again. A
declining window is brought to the front, so its prompt is visible. A
clean exit after a close request is recorded as a close on request. A
decline report is recognised after page output that lacks a newline.

Notes keeps a pending Save and close when asked again. It saves text
typed during that save before closing, and reports when it cannot save
because it is not connected.
2026-10-09 17:10:15 +00:00
..
.cargo feat(examples): add counter and notes demo apps 2026-03-12 15:31:20 +01:00
src fix(notes): keep Discard usable after a failed load 2026-10-09 09:05:25 +00:00
ui fix(appd): keep a session running while it answers a close, and add a forced stop 2026-10-09 17:10:15 +00:00
wit feat(examples): add counter and notes demo apps 2026-03-12 15:31:20 +01:00
app.wasm fix(notes): keep Discard usable after a failed load 2026-10-09 09:05:25 +00:00
Cargo.lock feat(examples): add counter and notes demo apps 2026-03-12 15:31:20 +01:00
Cargo.toml feat(examples): add counter and notes demo apps 2026-03-12 15:31:20 +01:00
signature.sig fix(appd): keep a session running while it answers a close, and add a forced stop 2026-10-09 17:10:15 +00:00
wapp.toml feat: let an application decline a close to keep unsaved changes 2026-10-09 17:00:08 +00:00