The official source of product insight from the Visual Studio Engineering Team
Let’s talk about the all-caps menus.
When we shared the RC design preview with you, we expected the uppercase menu would generate mixed feedback and emotions. We had seen similar reactions from early adopters and from our own internal users prior to posting about it. Rest assured that we’ve heard you, and we’ve been thinking through what should be done here. Using uppercase for the menus was not an arbitrary decision, and I think it will help the discussion to frame why we made this change.
We’ve chosen to use uppercase styling in the top menu for two main reasons: 1) to keep Visual Studio consistent with the direction of other Microsoft user experiences, and 2) to provide added structure to the top menu bar area.
On the first point, the use of uppercase text is becoming a strong signature element of styling for navigation and headings in Microsoft user interfaces. You can see it in the Azure Portal, in Zune, and in the latest Bing search results update.
On the second point, we explored designs with and without uppercase styling. In the end we determined it to be a very effective way of providing structure and emphasis to the top menu area in Visual Studio 2012.
Based on early feedback on this application of uppercase styling, we made two modifications to our design. First, we tuned the typography of the menu to better adjust to uppercase text, including increased spacing between menu items from 14px to 20px to make menu items stand out better. Secondly, we moved Quick Launch to the title bar to make more room on the menu bar, especially for cases where a user has installed add-ins that add their own top-level menus.
As with most style changes, there has been both positive and negative feedback. We realize that some of you will continue to dislike this change, and you’ve been very direct in expressing your opinions on this subject. Our view remains that this is the right design for the Visual Studio user interface for the reasons I mentioned above. That said, we will enable you to customize the casing, and we are exploring options for how to expose that choice. We will post again once we’ve settled on a final approach to be available in RTM.
THAT IS WHY BOOKS FOR THE PAST TWO HUNDRED YEARS HAVE BEEN USING ALL CAPS. OH WAIT, we use lower case to make it _easier_ to read. Maybe the UI designer(s) should go look up "bicameral script" before trying to justify their ignorance.
The tone of this article is like disciplining a three year old.
User: "I don't want all-caps menus! I like to see the first letter of each menu item already brought forward by relative height and blockiness. I submit that for every possible font and size, mixed case is more legible than all caps. Observe:
The only entry that is hard to locate in the first example, with no spaces whatsoever between items, is SQL - Because it is in all caps. The second one REQUIRES spacing to be at all legible. Will you restore this to the usual Office behavior?"
MS: "No. We are right about this."
User: "Please make it an option, at least. A toggle somewhere so that we can decide what works best."
The caps stays. And that's the end of discussion
Horrible. Just, horrible.
Hire better designers please.
CAN YOU REMOVE THE ALL-CAPS NOW?! AND YES, I’M YELLING AT YOU.