Skip to content

RFC: Tweak display/ordering ordering of drivers#382

Open
qwertychouskie wants to merge 1 commit into
MightyCreak:mainfrom
qwertychouskie:patch-2
Open

RFC: Tweak display/ordering ordering of drivers#382
qwertychouskie wants to merge 1 commit into
MightyCreak:mainfrom
qwertychouskie:patch-2

Conversation

@qwertychouskie

Copy link
Copy Markdown
Contributor
  • For vendors with multiple drivers, consistently use "older hardware -> newer hardware" ordering
    • By luck of alphabetical order, AMD (r600, radeonsi), Arm (lima, panfrost), Intel OpenGL (crocus, iris), and Nvidia (nv50, nvc0) were already ordered this way, but not Broadcom (v3d, vc4) and Intel Vulkan (anv, hasvk).
  • Order Translation before Software
    • Translation layers are much more likely to be intentionally used (e.g. modern Nvidia defaults to using Zink on NVK instead of the old nvc0 driver), while software drivers are almost always only used for testing or a fallback in case of broken hardware acceleration.
  • Remove square brackets around Translation and Software
    • I've been looking at this for a while, and it just feels very unnatural. If these truly need more differentiation, it should probably be done a different way, but as it stands now, the brackets feel like a downgrade.

For the square brackets, it's hard to explain the change beyond "feels wrong", but unfortunately that's often the nature of UI/UX, where it's often east to tell that something feels wrong, but not easy to tell/explain why.

- For vendors with multiple drivers, consistently use "older hardware -> newer hardware" ordering
  - By luck of alphabetical order, AMD (r600, radeonsi), Arm (lima, panfrost), Intel OpenGL (crocus, iris), and Nvidia (nv50, nvc0) were already ordered this way, but not Broadcom (v3d, vc4) and Intel Vulkan (anv, hasvk).
- Order Translation before Software
  - Translation layers are much more likely to be intentionally used (e.g. modern Nvidia defaults to using Zink on NVK instead of the old nvc0 driver), while software drivers are almost always only used for testing or a fallback in case of broken hardware acceleration.
- Remove square brackets around Translation and Software
  - I've been looking at this for a while, and it just feels very unnatural.  If these truly need more differentiation, it should probably be done a different way, but as it stands now, the brackets feel like a downgrade.
@qwertychouskie

Copy link
Copy Markdown
Contributor Author

Also, for making the table header always visible, it can be done much simpler than the recent change, and IMHO it feels much nicer to use as well, since it avoid the "scroll-within-a-scroll":

Screen.Recording.2026-07-04.at.4.56.59.PM.mov

It's as simple as setting style="position: sticky;top: 0;z-index: 1;" on that table row. If interested, I can open a PR reverting the previous change and implementing this method a bit later (have an errand to run rn).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant