You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are few useless information or seldom used input boxes which would be good to be removed probably.
The first candidates would be: the entire "projects search" block. It is huge and takes half of the output. It is better to move it to the bottom, after the main data which I need (the table with outdated packages) or remove it. Users can customize search from the main page if required.
The second is "outdated" and "ignored" columns in the table. Again, not very informative on mobile device but the first one takes a lot of space vertically, the second one would help to reduce it horizontally (and fit into a mobile resolution).
The text was updated successfully, but these errors were encountered:
Well I've had this idea for some time. At first I wanted to hide some columns and most of outdated versions with CSS, but that would likely be clumsy and won't help much, as pages will still be huge due to large version lists, and mobile seem to require completely different layout.
AMDmi3
transferred this issue from repology/repology-updater
Oct 4, 2019
Hi, I'm visiting the outdated page daily and use a mobile device quite often:
https://repology.org/projects/?inrepo=gentoo_ovl_pentoo&outdated=1
There are few useless information or seldom used input boxes which would be good to be removed probably.
The first candidates would be: the entire "projects search" block. It is huge and takes half of the output. It is better to move it to the bottom, after the main data which I need (the table with outdated packages) or remove it. Users can customize search from the main page if required.
The second is "outdated" and "ignored" columns in the table. Again, not very informative on mobile device but the first one takes a lot of space vertically, the second one would help to reduce it horizontally (and fit into a mobile resolution).
The text was updated successfully, but these errors were encountered: