luja
February 8, 2025, 7:08pm
1
Hi all,
I really like
But it lacks a filter for a qubes version. So If you look for your favorite piece of (vintage ) Workstation, you would like to know which qubes it has been tested for.
For example the Dell T7400 works fine with qubes 3.2 but who wants to operate qubes 3.2 if we have 4.2.4 comming up.
And this old fat work station (dual xeon 45nm) lacks some IO-MMU-feature, iirc, needed to run modern Qubes and thus is stuck with Qubes 3.2 to serve as an example. (Maybe, I test it again )
The Dell T7500 (Dual Xeon 32nm) should (will be tested soon) work with Qubes 4.2.4-rc1.
So having a filter button helps to get a better overview on which hardware can really be used with modern and not so modern Qubes.
Some more vintage hw is out then which is important for new users, especially if they want to donate hw to dissidents in poor countries.
Update:
T7500 with Q 4.2.4 rc1 does not work station
booted from stick, needs further research. Kernel panic after 2 black screens with blinking cursor (XEN?).
3 Likes
Well. You can sort by Qubes
column if you click on its header. But it is not very evident. I agree that a filter would be nice. I just looked at the open issues on Github and no one have ever asked for this.
1 Like
luja
February 8, 2025, 7:22pm
3
It should be obvious so the normal new user who wants to get a quick overview will be able to understand it.
Also it is a common reaction to test a new OS on something unimportant (the workstation your company just put on the garbage spot, which you rescued from the iron press and now sits in your garage). So having a good indication and selection helps users not to be frustrated if they want to give Qubes a try on a rainy weekend.
2 Likes
We have an open issue for this specific one:
opened 10:46PM - 18 Jul 21 UTC
C: website
ux
P: default
<!--(Before filing this issue, please read:
https://www.qubes-os.org/doc/issue-… tracking/
Please use this issue template. Do not delete it.)-->
### The problem you're addressing (if any)
<!--(A clear and concise description of the problem, if any, that this
enhancement is intended to address.)-->
@andrewdavidwong recently added the terrific functionality to the HCL table, of sortable headers. Hooray! Unfortunately, a few small interactive and visual cues are missing, to let folks know that in fact, these headers are sortable.
**Today's HCL Table**
No cursor-change or color change of the text on hover, to signify to users the item is live.
https://user-images.githubusercontent.com/8262612/126083911-36ed2bdc-75f2-46e8-ba12-6cabe5c0a1ac.mov
### Describe the solution you'd like
<!--(If you have something in mind, a clear and concise description of what you
want to happen. If you don't have something in mind, indicate as much.)-->
Generally I'm a strong advocate of interaction patterns documented by [patternfly.org](https://www.patternfly.org/v4) (maintained by RedHat, oddly enough!) or [Material.io](https://material.io/components/data-tables#anatomy) as a solid reference—yet both have specs for sortable headers, that kinda stink. Menus are more common to sort tables with, these days, as a pattern with richer options, than just table headers—which I suspect is why.
_Key attributes that are missing from today's implementation are:_
- The user's cursor should change when hovering over the general area of a sortable header
- The color of the header text should change on hover
- An icon of some sort should be visible both on static and on hover, to indicate sortability
- When the list changes direction, the arrow(s) should indicate that.
**Wikipedia**
Wikipedia's sortable table was mentioned in the Forum. It is highly usable, and is identical to the Bootstrap 4 spec for sortable table headers, but it is also quite busy/cluttered and lacks bolded headers that change color on hover. Like, the arrows don't **_have_** to be that big... but I'm also sure this implementation gets an A+ accessibility rating, which is not easy.
https://user-images.githubusercontent.com/8262612/126083921-d396f730-b3cf-474d-b7f7-cc9b9cd19783.mov
**GDrive**
Two different types of sorting. I do like the dot behind the arrow, as an extra "ting" of discoverability.
[This is the Material Style for Tables](https://material.io/components/data-tables/web#data-tables), that might be an option to implement?
https://user-images.githubusercontent.com/8262612/126083901-84c7c452-9ecc-4ec2-85c7-4ae6714c80d1.mov
**My Bank**
Note that often in tables, some headers are sortable and others are not. Users will probably expect that in this table, too. While I feel the arrows here and in the Wikipedia example, above, are needlessly clunky—you can't deny that they're not clear.
https://user-images.githubusercontent.com/8262612/126083896-c85ef6ff-31cd-4a5c-88d4-d8acfab203e0.mov
**Harvest**
My favorites of the ones I just poked around for, is from my invoicing software (Harvest). My only nits with it, are that 1. There should be pale gray arrows on hover, and 2. The column widths forcing the arrow to wrap onto the next line, is weird.
https://user-images.githubusercontent.com/8262612/126083906-04f41124-3894-4c1b-840a-b89c29af9a38.mov
TL;DR, my fav is the Google Material table, first. If you could literally implement just that. The Bootstrap Table standard would also get the job done. :)
### Where is the value to a user, and who might that user be?
<!--(Which users is this most likely to benefit? What user needs does this
address? How might a user summarize this change or new thing?)-->
Discussed [in forums](https://forum.qubes-os.org/t/plans-to-add-search-filter-functionality-to-the-hcl/5099).
### Describe any alternative solutions you've considered
<!--(A clear and concise description of any alternative solutions or features
you've considered.)-->
The current first implementation of sorting is a great first step, but regrettably the sorting is not discoverable.
### Additional context
Nopitty nope, nope.
-----
### Relevant [documentation](https://www.qubes-os.org/doc/) you've consulted
<!--(Provide a list of any relevant documentation you've consulted. We do not
know what you've already read unless you tell us. If you do not list anything,
we will assume that you haven't read any relevant documentation. If you're not
aware of any relevant documentation, write "None" (or "N/A" if not
applicable).)-->
### Related, [non-duplicate](https://www.qubes-os.org/doc/issue-tracking/#new-issues-should-not-be-duplicates-of-existing-issues) issues
<!--(Provide a list of any related issues of which you're aware. Do not
describe any other unreported bugs, features, or tasks here. We do not know
which issues you've already seen unless you tell us. If there is another issue
that seems like a duplicate, and you did not mention it here, we will assume
that you were not aware of it. If you didn't find any related issues, write
"None found.")-->
3 Likes