Bug 1024005 - anaconda white space could use some gestalt love
Summary: anaconda white space could use some gestalt love
Keywords:
Status: CLOSED DUPLICATE of bug 1039556
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-28 14:49 UTC by Ray Strode [halfline]
Modified: 2013-12-12 20:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-12 20:34:10 UTC
Target Upstream Version:

Attachments (Terms of Use)
lack of margins (56.12 KB, image/png)
2013-10-28 16:52 UTC, Matthias Clasen 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Ray Strode [halfline] 2013-10-28 14:49:07 UTC 
Matthias just did an install (see bug 1024000) for more details, and noticed there are no margins between the UI controls and the edge of the screen once package installation has begun.  Also there's a very wide gap between the controls up top and the progress bar down bottom.

That stage of installation would be more aestethically pleasing if the whitespace was shifted around a bit.
Comment 2 Matthias Clasen 2013-10-28 16:52:45 UTC 
Created attachment 816859 [details]
lack of margins
Comment 3 Matthias Clasen 2013-10-28 22:00:54 UTC 
this was an install in vm in gnome-boxes, in case it matters.
Comment 4 Chris Lumens 2013-12-11 15:44:05 UTC 
I am definitely not seeing this with an install of the beta tree.  Note that the reason there's a gap between the controls at the top and the progress bar is because there could be more spokes off this hub - we've got to leave some space for third parties, or us coming up with more stuff later on.
Comment 5 Chris Lumens 2013-12-12 20:34:10 UTC 

*** This bug has been marked as a duplicate of bug 1039556 ***
Note You need to log in before you can comment on or make changes to this bug.