I believe that it renders it significantly more difficult to read:
It’s not a real window (even a modal one), so I can’t even resize it.
My Environment
plasma-discover-0:6.8.2-1.fc44
I believe that it renders it significantly more difficult to read:
It’s not a real window (even a modal one), so I can’t even resize it.
plasma-discover-0:6.8.2-1.fc44
One could say your window is uselessly wide.
The lines of text are not long, so making the popup wider wouldn’t gain you anything either.
IMO the problem is not the presentation of the container but the fact that this happens at all.
Which is tricky to avoid on traditional package-based distros without hiding potentially important information; you’d surely want to know if a broken update is about to remove Plasma or the kernel, right?
To demonstrate. I noticed this in practice, when I had it tiled to 50 % of its depicted width, because 1⁄2 of the 2 560 px of my monitor is 1 280, which, at 100 % display scale, approximately equates A4 width.
It would prevent the lI:markers from wrapping with their content. That is one of the reasons why list-style-position: outside; is the default for browser stylesheets.
That what “happens at all”? I can’t say that I’ve been able to ascertain what you refer to. If you’re referring to the window not adapting to its content, then yes; we appear to agree. Even a hard-coded maximum of A4 width would be an improvement.
I’m referring to the need to warn users that an update will remove some packages, which is what this popup is trying to communicate.
Ascertaining the safety of a package removal requires users to distinguish between those that are benign and expected vs those that are unexpected and dangerous.
But “benign and expected” and “unexpected and dangerous” are subjective descriptions that require the user to understand a great deal about the internals of the system and how their OS does package management!
Discover is intended to be user-friendly, but the need to expose this technical detail breaks that user-friendliness. Yes, I can see how the popup being slightly too narrow and unresizable is a small irritation, but in my opinion the real problem is that it is being shown at all.
@ngraham, determining which things are important definitely is difficult via Discover. I tend to find that dnf5’s table output is a little easier, although a column for whether dnf repoquery --userinstalled would help the most.
Consequently, I agree with that conceptual idea, if something else can genuinely replace the overlay. However, what I’m really discussing (in this topic) is actually the sheet itself, rather than its purpose. This overlay is utilised elsewhere, and it never appears to choose a useful size, whatever it is being utilised for.
Even if not a real window (which appears to be increasingly desirable for Kirigami software, for whatever reason that I don’t ever seem to be able to understand), having it either fill the view, as a new page, or be resizable, would be preferrable.
On AOSP, almost all modal pseudo-windows have recently been replaced with full-screen activities, to mitigate the problem that window-like overlays, when not real windows, tend to be worse than both alternatives.
Yeah, I don’t disagree.
Making it wider would be relatively easy. Using a full page would be harder, since this overlay pops up automatically in response to the update system itself communicating something to Discover, not any user-initiated action. So it really is a sort of in-your-face “hey maybe you should look at this before proceeding” kind of UI.
Perhaps, a panel (filling the bottom half of the viewport), with a semantic-warning-colour background, would work. Somewhat like the venerable QDockWidget of olde: