mirror of
https://github.com/retspen/webvirtcloud.git
synced 2026-04-26 16:05:58 +03:00
[GH-ISSUE #222] Feature request: Grouped instances page - collapsed by default #149
Labels
No labels
bug
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/webvirtcloud#149
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lord-kyron on GitHub (Jan 25, 2019).
Original GitHub issue: https://github.com/retspen/webvirtcloud/issues/222
@catborise - in a scenario, when there are several computes, I would like to have an option to choose a collapsed by default grouped instances page - again choosable from the settings.py, like the grouped and non-grouped variants. I would like this, because when I have 5-6 compute hosts added to webvirtcloud and I have 5-10 VM Instances on every single of them, I have to scroll down and the default instances screen looks overlapped with information and difficult to navigate trough all those instances without confusions some times. A variant of the instances page collapsed by default will allow me to choose a host and look only at his instances expanded. No other features ar needed - just collapsed by default compute hosts.
Can you make this possible?
Thank you!
P.S. - I know that you can collapse all, by clicking on the "#" icon on the top row, but it will feel more nicer if when I log in, they are collapsed by default. :)
@catborise commented on GitHub (Jan 28, 2019):
hi bandic, Actually there is nothing collapsed only hide table rows. May be we call hide script. i could not add the choice for that option. it affects other things
you can add this script to alinstances.html
$( document ).ready(function() {
hide_all_host_instances();
});
@lord-kyron commented on GitHub (Jan 28, 2019):
@catborise - thank you! It is working more than fine!