ubuntu / ubuntu/Tiling-Assistant
Revisiting the OOTB experience and main settings
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.3k
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
I am reviewing the current state of Tiling Assistant and would like to improve (aside from the code 🙃) the OOTB experience and main settings (i. e. no advanced/experimental stuff that's hidden away for now). I am concerned about the discoverability of features and the terminology I've used so far. Especially, the names of
- the Dynamic Keybinding Behaviors
- the Monitor Switch Grace Period
- and the Window Grab Modes
don't communicate what they do well. But I couldn't come up with better terms...
As for the discoverability: most features can only be discovered by looking at the preference window and finding a related setting. The window grab modes are especially bad since the only way to be aware of them is to read the repo's wiki. To at least fix the window grab modes, I thought that highlights could be added to the screen edges/quarters when a window is grabbed to indicate them as 'drop targets'. Maybe also have a small pills/popup appear at the bottom of the screen to hint at/list the grab modes in a subtle manner. Question is, whether that is too annoying for people who already know about those features. A nice animation, a setting to disable it and only enabling it on 'new installs' might be enough to address those concerns...
Here is a screenshot of the default settings (as of v39)

Contributor guide
No contributing guide indexed for this repository
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 preference window and the linked wiki pages for Dynamic Keybinding Behaviors, Monitor Switch Grace Period, and Window Grab Modes. The issue does not name files or tests; done would require an agreed terminology and a defined, non-intrusive way to make window grab modes and main features discoverable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- design, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100