-
Notifications
You must be signed in to change notification settings - Fork 7
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
Hide Default Group No Resources from Machines section (and column headings on remote machines) #192
Comments
Yeah, I noticed that, though this might be mitigated by limiting character number in Machine name. |
Might be nice to have an option to hide all groups with no resources, unless that would leave none visible. |
I think just a Default Group with no resources should be hidden, as other groups might have no resources temporary while user is setting things up, and that might cause a lot of questions for new users. |
Seems reasonable. If you have a wide screen. |
I think it makes sense to not require the default group. Internally, the default group has the empty string as its name and it cannot be deleted. If you could rename the default group and delete it just like any other group then this wouldn't be an issue. The other issue of combining the machine and groups sections in to one table makes some sense. As @kbernhagen mentioned, it leaves no place for the group or machine action buttons. Finally, we have to strike a balance between the dense table view expert folders might like and a more user friendly view that makes F@H less daunting for new users. And it still needs to be usable on mobile screens. |
Would it be possible to add colour coding for different machines? To give more contrast where one machine starts and another ends? |
Currently units have a group name, but that group is not guaranteed to exist. If a unit’s group has been deleted, the unit seems to belong to the default group. If you remove group “” and a user has multiple groups created, which of those groups should be treated as the default group when a unit must be moved? |
Might also want to disable deleting a group that has units or is not paused. |
Note that a GPU unit that gets moved to a group with no appropriate GPU will be stuck paused for insufficient resources. |
I think just hiding it from main page would be sufficient. As far as I understand, removing Default Group is out of the question due to technical reasons. Obviously deleting user created groups while that group is folding a WU should not be allowed |
v8.4.5 add some extra columns: I still don't see a good way to display machine and group actions. One idea would be to have a separate table of machines and groups with no WUs and only show WUs on the WUs tab but then you have to move back and forth. Another idea is to have a popup with all the machine and group actions. I'm still not sold on either of these ideas. |
I played around with different resolutions and monitor ratios. While my sketch proposal would work on normal 16:9, 16:10 or wider screens, it fails miserably with 4:3 ratio screens, unless users with such monitors majorly sacrifice amount of info columns they can add to main page without scrolling horizontally. |
I know we spoke about this before, that disabling Default group is a bit of the undertaking. Would it be possible to just hide it from Machines section Default Group if it does not have any assigned resources to it? At the moment UI gets quite busy, and that extra line per machine with that triangle at the end gets very distracting if one is monitoring their machines. Plus it would save some real estate vertically, so more remote machines would be visible without the need of scrolling down.
And maybe even hide column headings (Status, Project, RCG, Core, etc) for all but local machine. Here is an example of what I mean:
So now if I glance at the bottom screenshot, I can easily see all the groups and machines are folding, and none are paused, while the first screenshot would make me double check, since I would spot these "Start" triangles at the end.
Thanks
The text was updated successfully, but these errors were encountered: