Open flourish86 opened 5 years ago
Basically it makes sense. Though, doesn't it differ too much from how we're utilizing tabs everywhere else? All views with tabs I can think of provide tabs if there's more content available that is somehow specifically related. (e.g. The host and service detail view)
Even the System -> Monitoring Health
menu does provide tabs which are both related to an Icinga instance. The only exception here are the Configuration
menus.
Even if this is a non-issue, the menu is only visible when unfolded. So, is this really required to change after half a decade? (Of course, this may exactly another reason why it's okay to change...)
Eh, anyway. Just my two cents.
Current Overview Submenu
The Overview is pretty crowded and could therefore be more streamlined if we condense associated submenu items.
Currently
Streamlined Submenu
We should make use of tabs for an additional hierarchy level and put the group items in tabs within the respective submenu item view.
This would result in the following structure for the Overview submenu:
For example in Hosts View