tiny-pilot / tiny-pilot/tinypilot
Design: How does the user trigger actions from the status bar?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.5k
- Forks
- 291
- PR merge metrics
- No merged PRs in 30d
Description
Currently, TinyPilot's status bar is purely informational. It shows information to the user, but clicking on the status bar does nothing.
Over the past couple of years, we've discussed a few instances where it would be useful if the user could trigger an action from the status bar:
- https://github.com/tiny-pilot/tinypilot/issues/1511
- User can turn off key history from the status bar
- User can open the video settings page from the status bar
We should think about what adjustments we'd need to make to the status bar to go from making it informational-only to having a mix of informational and controls that can respond to clicks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current status-bar implementation and issue 1511, then compare the proposed key-history and video-settings actions. Define how informational content and clickable controls should coexist, including what actions are exposed and how users recognize them; the issue is done when the interaction design and required adjustments are agreed.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100