Replies: 1 comment 2 replies
-
Hey 👋 Thank you for your detailed proposal + putting it under GitHub discussion 🙏 Answering in a reverse order:
Some users (especially beginners) use this tool to "explore" their units + this tool should also allow users to familiarize themselves with systemd. I prefer the existing structure over a "dynamic" component that pops in and out.
Similar to the above. The tool should invite users to explore and I find the default layout aesthetically pleasing. 1 & 2: Fully agree with this proposal. I am currently working on #43 and depending on how it "feels" in the end I might reconsider my answer but I agree that it would be nice to "expand" the vertical space once a user jumps to the preview pane. I will see how jarring it will be but I would also provide an option to disable this "animation" and provide a keyboard shortcut for toggling the height. |
Beta Was this translation helpful? Give feedback.
-
There are currently three main panes: search input, results, and unit tab group. The unit tab group takes up about 1/3 of the height of the screen:
That ratio makes sense when scrolling through search results and the user's focus is on finding the "interesting" unit. However, once the interesting unit is found, and the focus is shifted to the unit's tab group pane, it seems like a bit of a waste of space to only be using 2/3 of the screen to show the data in the tab groups.
Options:
When tabbing from the search results to the unit tabs, shrink the search results height to just show the single unit that is currently selected. It's possible this auto-resizing could be jarring to a user.
Give a keyboard shortcut to maximize the tab group height
Adjust the heights so that the search results only take up 1/3 of the height at all times. Given that searching filters the results real-time, it seems like less vertical space to view the results would be acceptable.
Remove the search results pane as a fixed height pane and instead show it as a modal/popup when searching (like google auto suggest results while you are still typing search terms). That leaves the unit tabs to use almost the entire screen while still preserving most of the functionality of the existing layout.
A one drawback is that the tabs pane content will be covered by the search results until a unit is chosen. I don't think this will be a problem in practice b/c when the user has identified the unit they care about, they just select it and the search results box disappears (getting out of the way). Additionally, the search results box should expand and collapse as the number of results narrow. So, most of the time, the results box will be pretty short with just a handful of characters of search input.
A nice symmetrical property of this is that, assuming the need to focus the tab content pane goes away (Request: UX enhancement for service tabs #43), there are only two panes to focus on. Search (with results modal which disappears) and unit tab tab panes. So there is never a need to shift+tab. It's always just tab to go back and forth between finding a unit (search) and reviewing a unit (tab panes).
Beta Was this translation helpful? Give feedback.
All reactions