Shell 3: Spike — Wayland global shortcuts through the portal #795

Closed
opened 2026-11-17 23:02:33 +00:00 by charles · 0 comments
Owner

Task 3 of the Desktop shell plan (docs/superpowers/plans/2026-11-17-desktop-shell.md, section "### Task 3:"). The plan on the shell branch is the source of truth; this copy is for reading.

Closes: — Depends on: — Time box: two days.

Files:

  • Create: crates/fluxer-platform/examples/portal_shortcuts.rs, crates/fluxer-platform/tests/portal_shortcuts_bus.rs (fake org.freedesktop.portal.Desktop with GlobalShortcuts v1 and v2 and host.portal.Registry)
  • Modify: crates/fluxer-platform/Cargo.toml (ashpd 0.14, Linux only, no default features beyond what is needed), Cargo.toml, deny.toml if needed, README

Interfaces:

  • Proves with ashpd: Registry.Register("flaxative") before any other portal call (and what happens without an installed flaxative.desktop), CreateSession, ListShortcuts, BindShortcuts with ids voice_toggle_mute, voice_push_to_talk and a preferred trigger, Activated / Deactivated as press and release, ShortcutsChanged, ConfigureShortcuts when version ≥ 2, the session surviving a portal restart or not.

  • Records by hand on this machine (KDE Plasma 6 Wayland): the dialog, where the keys are changed, hold behaviour — whether Deactivated arrives on release, what tapping another key during a hold does (KDE bug 484525), a trigger with modifiers, a mouse button as trigger. From documentation: GNOME 48+, Hyprland (hyprctl globalshortcuts), Sway and COSMIC (no portal interface).

  • Produces the fake portal harness for Task 28.

  • Step 0: the example binds two shortcuts and prints press <id> / release <id> (ids only, never keys).

  • Step 1: registers_before_first_call, bind_then_activated_and_deactivated, empty_bind_answer_is_denied, shortcuts_changed_reported, configure_only_on_v2, portal_restart_detected.

  • Step 2: commit spike(platform): global shortcuts portal; report, with the measured hold behaviour.

Task 3 of the Desktop shell plan (`docs/superpowers/plans/2026-11-17-desktop-shell.md`, section "### Task 3:"). The plan on the `shell` branch is the source of truth; this copy is for reading. **Closes:** — **Depends on:** — **Time box:** two days. **Files:** - Create: `crates/fluxer-platform/examples/portal_shortcuts.rs`, `crates/fluxer-platform/tests/portal_shortcuts_bus.rs` (fake `org.freedesktop.portal.Desktop` with `GlobalShortcuts` v1 and v2 and `host.portal.Registry`) - Modify: `crates/fluxer-platform/Cargo.toml` (`ashpd` 0.14, Linux only, no default features beyond what is needed), `Cargo.toml`, `deny.toml` if needed, README **Interfaces:** - Proves with `ashpd`: `Registry.Register("flaxative")` before any other portal call (and what happens without an installed `flaxative.desktop`), `CreateSession`, `ListShortcuts`, `BindShortcuts` with ids `voice_toggle_mute`, `voice_push_to_talk` and a preferred trigger, `Activated` / `Deactivated` as press and release, `ShortcutsChanged`, `ConfigureShortcuts` when version ≥ 2, the session surviving a portal restart or not. - Records by hand on this machine (KDE Plasma 6 Wayland): the dialog, where the keys are changed, **hold behaviour** — whether `Deactivated` arrives on release, what tapping another key during a hold does (KDE bug 484525), a trigger with modifiers, a mouse button as trigger. From documentation: GNOME 48+, Hyprland (`hyprctl globalshortcuts`), Sway and COSMIC (no portal interface). - Produces the fake portal harness for Task 28. - [ ] **Step 0:** the example binds two shortcuts and prints `press <id>` / `release <id>` (ids only, never keys). - [ ] **Step 1:** `registers_before_first_call`, `bind_then_activated_and_deactivated`, `empty_bind_answer_is_denied`, `shortcuts_changed_reported`, `configure_only_on_v2`, `portal_restart_detected`. - [ ] **Step 2:** commit `spike(platform): global shortcuts portal`; report, with the measured hold behaviour.
charles added this to the Desktop shell milestone 2026-11-17 23:02:33 +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#795
No description provided.