konsumer / konsumer/web-zen-dev
input: keyboard
Open
- Dominant language
- C
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
I think it should be mapped to canvas keyboard events (the same canvas used for framebuffer?) I think it should go in `/dev/input/keyboard` or `/dev/input/eventX`
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue mentions canvas keyboard events, the framebuffer canvas, and the paths /dev/input/keyboard or /dev/input/eventX, but no repository files or tests. First locate the existing framebuffer, canvas, and input entry points, then determine which input path the project uses; done means keyboard input is mapped consistently and covered by an appropriate test or documented verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, wasm
- Domain
- game-dev, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100