klubhaus/sideline
2
0
Fork 0
forked from genewildish/Mainline
Code Issues 5 Pull Requests Projects 1 Releases Wiki Activity

Epic: Usable Interaction Model for Displays and Keybindings #51

New Issue
Open
opened 2026-03-21 22:37:48 +00:00 by david · 0 comments
david commented 2026-03-21 22:37:48 +00:00
Owner
Copy Link

Summary

Create a comprehensive interaction model for Mainline displays and keybindings to ensure usability and accessibility.

Problem Statement

The current display and keybinding system needs a standardized interaction model that provides:

  1. Consistent keybindings across all display backends
  2. Accessible UI for users with different input methods
  3. Configurable controls for custom workflows
  4. Clear documentation of available interactions

Proposed Interaction Model

Display Backends

  • Terminal: Keyboard-only navigation, ANSI escape codes
  • Pygame: Keyboard + mouse support
  • ModernGL: Keyboard + mouse + gamepad (future)
  • WebSocket: Remote control via web interface
  • Multi: Composite of multiple displays

Keybinding Categories

  1. Navigation: Scroll, pan, zoom controls
  2. Effect Control: Toggle, adjust intensity, reorder effects
  3. Pipeline Control: Start/stop, pause, reset
  4. Display Control: Switch display modes, toggle UI panel
  5. System: Quit, help, configuration

Implementation Tasks

  • Audit existing keybindings across all backends
  • Define unified keybinding schema
  • Implement configurable keybinding system
  • Add keybinding help/overlay UI
  • Document interaction model in README

Related

  • Dependent on: ModernGL display backend (issue #42)
  • Related to: Pipeline mutation API
  • Skills: mainline-display, mainline-architecture
## Summary Create a comprehensive interaction model for Mainline displays and keybindings to ensure usability and accessibility. ## Problem Statement The current display and keybinding system needs a standardized interaction model that provides: 1. **Consistent keybindings** across all display backends 2. **Accessible UI** for users with different input methods 3. **Configurable controls** for custom workflows 4. **Clear documentation** of available interactions ## Proposed Interaction Model ### Display Backends - **Terminal**: Keyboard-only navigation, ANSI escape codes - **Pygame**: Keyboard + mouse support - **ModernGL**: Keyboard + mouse + gamepad (future) - **WebSocket**: Remote control via web interface - **Multi**: Composite of multiple displays ### Keybinding Categories 1. **Navigation**: Scroll, pan, zoom controls 2. **Effect Control**: Toggle, adjust intensity, reorder effects 3. **Pipeline Control**: Start/stop, pause, reset 4. **Display Control**: Switch display modes, toggle UI panel 5. **System**: Quit, help, configuration ### Implementation Tasks - [ ] Audit existing keybindings across all backends - [ ] Define unified keybinding schema - [ ] Implement configurable keybinding system - [ ] Add keybinding help/overlay UI - [ ] Document interaction model in README ## Related - Dependent on: ModernGL display backend (issue #42) - Related to: Pipeline mutation API - Skills: mainline-display, mainline-architecture
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
epic:#2
epic:#20
epic:#3
epic:#4
epic:#5
epic:#6
epic:Data Source
epic:Display Backend
epic:Display Tools
epic:Effects
epic:Pipeline Architecture
epic:Sensors
status:feature-complete
status:in-progress
status:released
status:tested
type:epic
type:epic
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
david genewildish
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: klubhaus/sideline#51
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?