Description of problem:
When VM details are being viewed, 3 panes become available – top list, bottom details and the events panel ( bottom tab) and there is no way to maximize any of these panes effectively. Customer wants to reclaim real estate and have the ability to make any one of these full screen with a click – pop-out panels. The pop-out panels can be read-only. Popping out Events is desired especially.
This is needed because user is Running out of real estate when single screen presents too many levels of information
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Another use case that points to the need to maximize certain sections of the console - User would like to have the ability to close down the detail sub tabs at the bottom of a list when a row is selected above. Today, the only way to do that is to go to a different tab and return. “We do this a 100 times a day and it gets annoying”
Related bug pointing to the need of the user to adjust the distribution of screen real estate - Bug 999713
*** Bug 962879 has been marked as a duplicate of this bug. ***
We should probably open a new bug on the following issue but since it's the same view I'll describe the problem and solution here. We can then open a new bug for it.
The lower pane description looks awful and is not readable anymore.
We should seriously consider changing the alignments of name to the right and changing the colours of the values.
Take a look at my sketch.
Created attachment 822043 [details]
problem and solution of lower pane
In 4.2 ui re-design, we'll have the object details in a new page, resulting in much more space, so that will no longer be needed.
Adding proper dependency.
This won't support popping out the details to a new dialog, but it will give more space.
Tasks, Events and details also are now opened in whole page view.
verified in ovirt-engine-4.2.0-0.4.master.el7.noarch
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:
[No relevant external trackers attached]
For more info please contact: firstname.lastname@example.org
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.