New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to filter or sort HCL page entries by Qubes release #3795

Open
andrewdavidwong opened this Issue Apr 7, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@andrewdavidwong
Member

andrewdavidwong commented Apr 7, 2018

A user has requested that we add an option to the HCL page that allows one to view hardware entries according to the Qubes OS release for which the report was generated. One possibility is to create a feature that filters out all releases except one. Then, a visitor could click a button for a particular release to see only entries for that release. Another possibility is to make the "Qubes" column sortable so that all the entries from one release are grouped together. (However, they would still be segregated by platform type.)

CC: @Zrubi, @tasket

@andrewdavidwong andrewdavidwong added this to the Documentation/website milestone Apr 7, 2018

@tasket

This comment has been minimized.

Show comment
Hide comment
@tasket

tasket Apr 8, 2018

I wondered if we should do this... the table is getting rather large and harder to browse.

My first inclination is to highlight or grey-out rows depending on the Qubes version. This sidesteps problems with sorting models that have multiple version entries and whatnot. It also keeps the page more coherent as nothing is shifting around. Lastly, I think it can be done without adding stuff like 3rd party jquery plugins.

tasket commented Apr 8, 2018

I wondered if we should do this... the table is getting rather large and harder to browse.

My first inclination is to highlight or grey-out rows depending on the Qubes version. This sidesteps problems with sorting models that have multiple version entries and whatnot. It also keeps the page more coherent as nothing is shifting around. Lastly, I think it can be done without adding stuff like 3rd party jquery plugins.

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Apr 8, 2018

Member

I would be fine with that approach. I wonder, though, whether it provides the reader much benefit beyond what can be achieved by using the built-in browser page search functionality to highlight every occurrence of the desired version number.

Member

andrewdavidwong commented Apr 8, 2018

I would be fine with that approach. I wonder, though, whether it provides the reader much benefit beyond what can be achieved by using the built-in browser page search functionality to highlight every occurrence of the desired version number.

@Zrubi

This comment has been minimized.

Show comment
Hide comment
@Zrubi

Zrubi Apr 17, 2018

Member

I think the current design can only be improved using:

  • database (like) backend
  • javascript table filtering: datatables.net

I would go with the javascrip direction - if we really need any better than the current one.

Member

Zrubi commented Apr 17, 2018

I think the current design can only be improved using:

  • database (like) backend
  • javascript table filtering: datatables.net

I would go with the javascrip direction - if we really need any better than the current one.

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