Workspace switcher: one-click buttons and a visible sign of the current workspace
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
Start by finding the current workspace switcher, the menu behind the workspace name in the sidebar header, and the "Switch to workspace" search entry, to see how workspace colour and icon are shown today. The open questions are where the buttons go, whether the colour may tint the app, and which keyboard shortcuts to use, so settle those with the maintainers before writing code. Done means a design agreed in the thread and then an implementation that meets AA contrast in light and dark themes.
Written by the indexing model from the issue text.
Description
Suggested by Seventy-9DegreesNorth in #755 (item 4).
Problem
Switching workspaces feels like leaving for another program, and once there it is easy to lose track of which workspace you are in. Today the switcher is a menu behind the workspace name at the top of the sidebar (with each workspace's icon or colour and its Inbox and Today counts), also reachable from search with "Switch to workspace". A workspace's colour and icon show only in that small header control; the rest of the app looks the same in every workspace.
What the reporter would like
- Switch with one click from a row of buttons, one per workspace, instead of opening a menu.
- A clear, gentle sign of where you are: the workspace's colour as a highlight or tint, and a bigger icon branding the space. "Not crazy, just highlights."
Things to decide
- Where the buttons live (the sidebar header, a narrow rail, the bottom of the sidebar), how they scale past a handful of workspaces and how they fit on a phone.
- Whether the workspace colour may tint the app (for example the accent or the sidebar header) and how that combines with the user's theme and accent, in light and dark and at AA contrast.
- Keyboard: a shortcut per workspace (for example in the
gsequence).
- Dominant language
- Go
- Stars
- 9
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from pixari/OpenTodo
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
documentation enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Calendar: a Quarter view between Month and Plan, and 3-day / custom spans in PlanPossibly taken @AIDockerCloud claimed this 1 day ago. Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
after-1.0 area: integrations enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
koordinator-sh/koordinator#3257 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
Component: Backup and Restore Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
needs-acceptance wg/router-models-inference-runtime
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vllm-project/semantic-router#6018 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
eugenioenko/ttt#1461 ·
Maintainers usually reply within 1 day