GNOME Bugzilla – Bug 702714
classic session: the application menu occupy much space on the screen
Last modified: 2015-03-07 02:51:26 UTC
Created attachment 247301 [details] space left In large monitors, the application menu can occupy half of screen (vertical) and third screen (horizontal), while small monitors, can occupy more than two thirds of screen (vertical) and almost half of the screen (horizontal). In projectors (usually 800x600 yet) occupies nearly the entire screen. At a glance, one might gain some vertical and horizontal space, you could also remove one of the categories that repeated applications ("other"?)
Created attachment 247302 [details] application menu (mockup) To make a small mockup of how it would look aplicacón menu. It makes better use of vertical and horizontal space. As an idea, I added a separator to differentiate the activities menu.
I agree with this proposal for improvement. Beyond aesthetic problem, there is a practical one. I have been using the GNOME classic session for a while, and it really becomes a problem when using the application menu from a projector. Decrease the space occupied by the application menu (or put another way, saving screen space), would be a good solution to this problem.
Yes, it makes sense to reduce the width a bit.
(In reply to comment #3) > Yes, it makes sense to reduce the width a bit. Do you could also adjust the height of the menu? The use of the categories in the menu is dynamic because it depends on if we have installed an application belonging any predefined category. So I think the height of the application menu must also be dynamic. (perhaps with a minimum to ensure usability) Many users have maybe just basic applications, the application menu take up much space showing lot of empty space. Moreover, the application menu also displays the folders "utilities" and "sundry", repeating many of the applications that can be found in other applications menu categories.
(In reply to Allan Day from comment #3) > Yes, it makes sense to reduce the width a bit. This was done now. *** This bug has been marked as a duplicate of bug 745670 ***