Slashdot Mirror


Microsoft Ignores Usability With All-Caps Menu in Visual Studio

mikejuk writes "The recent release of Visual Studio 2012 contained a UI element that few believed could make it into the final version — ALL-CAPS menus. After lots of user criticism and disbelief, Microsoft has moved swiftly to do something about it — by tweaking the typography. '... 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.' This must be a new meaning of the word 'structure,' because putting the menu items into all-caps means that they are all the same height. When each menu items starts with a cap then there is structure because you can see the change in height, marking the start of the next menu item. The idea that putting a menu into all caps adds structure is something that is very difficult to see. If you wanted to put structure into a menu, well how about color? Oh wait, I forgot the design department dumped color in favour of the 'everything-is-grey UI.' Developers are the people who invented CamelCase to make sure that the structure of run together words would stand out better — and now we are asked to believe that making a menu all-caps adds structure. I don't think so."

14 of 415 comments (clear)

  1. All of the "new UIs" by Anonymous Coward · · Score: 2, Interesting

    It seems that all of the newest UIs - whether they are from Microsoft, Google, Apple, etc. - all suck. They are flat, colorless, abominations where you can't even tell what the user interface elements do or if they are even supposed to be user interface elements. I spent a good amount of time yesterday and today in Visual Studio 2010 and it has a very nice UI. I know they need to "newify" everything in order to say "new and improved" - but damn. All upper case, all grey, all lame.

    1. Re:All of the "new UIs" by Anrego · · Score: 3, Interesting

      Totally agree.

      I think it's being driven by the cell phone / tablet craze. Everyones trying to make their desktop look like their cellphone. I too think it's a major step backwards.. and I think a lot of the UI design guys are out of touch with what people actually want.

  2. Relearning... by Atzanteol · · Score: 5, Interesting

    As I understand it road signs (or many of them) in the UK used to be in caps but studies showed that mixed-case was much easier to read (which mattered more as cars got faster) since we're looking for familiar patterns.

    Looks like Microsoft will need to re-learn this lesson...

    --
    "Ignorance more frequently begets confidence than does knowledge"

    - Charles Darwin
  3. Structure by Talderas · · Score: 3, Interesting

    When each menu items starts with a cap then there is structure because you can see the change in height, marking the start of the next menu item.

    Call me blind. But this rant is blown out of proportion. He's complaining about structure, yet there is a very clearly delimited blank space between menu items a blank space which is much large than present in the mixed case version. In fact, I find it a lot easier to read the menu item word in the all capital version compared to the mixed case most based on the large spacing alone.

    --
    "Lack of speed can be overcome. In the worst case by patience." --Znork
  4. Re:well, after all... by TWX · · Score: 3, Interesting

    it is from MicroTard, so whadja expect?

    Regardless of one's feelings on Microsoft, that company has consistently and continually tried to make their user interfaces as attractive and easy to use as is possible. They've gone through the effort to develop fonts, to determine how to add pseudo-3d effects, how to space things and how to define icons and sizes. Whatever your beef with Redmond, the UI is the one thing that I will wholeheartedly disagree with you about in almost all circumstances.

    If they dropped the ball here, then that's absolutely amazing. Literally amazing. They've built a company and made some of the richest people in the world on how pretty and easy to use their software products are, at the expense of what those interfaces run on for lower level code. If they're losing touch with UI now, that doesn't bode well for them for the long term. They certainly won't disappear, but their non-OS products would lose market share and once people stop being locked in to their non-OS products, they have little reason to stay with the OS itself if other vendors have multiOS versions of competing products.

    --
    Do not look into laser with remaining eye.
  5. Ribbon menu by avandesande · · Score: 5, Interesting

    How come they haven't created a 'ribbon menu' for Visual Studio? Perhaps this is tacit admission that the Ribbon Menu sucks and is inefficient.

    --
    love is just extroverted narcissism
    1. Re:Ribbon menu by cbhacking · · Score: 3, Interesting

      Ribbon is quite the opposite of inefficient, in terms of finding things and clicking them. Some people claim to be incapable of operating it properly, but I truly do not understand this. It groups and sub-groups in a way similar to a menu, but with much more visible at-a-glance, without submenu delays, and with more images and less text. Additionally, sections are shown when relevant and removed otherwise, instead of having a fixed menu bar that, if you don't have an image slelected (for example), is clickable but has every option under it greyed out.

      The problem with the ribbon is that, while it aids discoverability and rapidly performing common actions, it's less space-efficient. Given the truly phenomenal number of configurable options and user-initiatable actions in Visual Studio, it might just not be possible to fit a suitable number of items on a ribbon for any display of less than excellent horizontal resolution. Sure, many developers will have such a display, and for them (us), an optional ribbon might actually work very well. For people still coding on screens less than 1500 pixels wide or so, or for people who like to tile Visual Studio with another window on the same screen, the ribbon would just be too truncated.

      --
      There's no place I could be, since I've found Serenity...
  6. ESL by xdor · · Score: 2, Interesting

    Developing software for a global bank many moons ago, the software recipients preferred/required capitalized menu items and input fields. As English was not their first language, they explained that CAPS were easier for them to read.

    So either Microsoft's focus group is global or their developers are

  7. Re:Hands Off by wmac1 · · Score: 3, Interesting

    Not everyone does the job for fun.

    I have been doing all my development work in Eclipse for the last 5-6 years. However for this specific Windows C++ project I needed to use Visual Studio. Like it or not I have a life to manage. Otherwise why would I do programming day and night at the age of 40, with a PhD in computer science? Salary of a PhD university staff is less than $1500/month and that's not enough (considering that I spent savings of 10 years of my hard work to reach the PhD dream of mine).

    When I turned into Visual studio 2012 RC hoping that it will provide better compiler, error messages, error preview and editor, I could not bear it even for 20 minutes:

    - The error list uses dark gray texts on gray background (my almost old eyes could not bear it...).
    - Clicking on an item in errors list would open the source on bottom output/error dock! in a new tab.
    - Tabs were on bottom (like the class and solution explorer), now they occupy additional space on top.
    - Menus are caps
    - You feel bored in a gray and flat environment after 12 hours of programming daily ...

  8. Re:Are you surprised? by MrAngryForNoReason · · Score: 4, Interesting

    This is the company that gave us the ribbon.

    I understand that if you are someone who knew exactly where every option was then the ribbon would be a step back. But from my point of view it makes it much easier to find features that were previously buried in the menus.

    The point of the ribbon is to expose useful features to the user so they actually use them.

  9. Re:MS are fully into change-for-its-own-sake mode by Anonymous Coward · · Score: 2, Interesting

    I just wanted to say M$ isn't the only one 'solving' problems nobody but a loud-whining-few had.

    We can looks to scores of changes to many OS' and respective UIs, only half of which real people wanted or even needed. Yet simple things we asked for that actually affect our lives seem to never get addressed properly.

    Decades later, we still have the notion that in order to eject a cd, you need to throw it into the trash bin! Regardless of the used-to-be-functional button on the drive itself, which of course is disabled because....."we know better"

    Or, point your finger at ANY linux distro and claim multiple monitors works right, I dare you. But hey, taking UI element control OUT was the way to go there right?!
    Yes Gnome, staring at your collective asses. I won't even go into the other poor attempts some have made.

    What gets me, is the ideas in computing now seem to be as lame as the ideas coming out of Hollywood. "Let's make it all shades of grey, you know so it looks hip!" - who here honestly didn't see that in their heads? These ideas are being fed to us as if they are new, as if they help us somehow, they aren't and they don't, unless of course you are trying to do work on some underpowered toy with no real input options designed for work, speed, ergonomics....shit, anything that drove peripheral improvement over the last 20 years.

    Newest version of FF is an example....now on what used to be a clean start page, I have monstrous buttons for things I almost never use.....all to make some future tablet user happy. Thanks for the awful waste of space guys! Rock on!

    I swear this shit looks like it was developed over at Playskool.

  10. changed in 1965 in the UK after 1958 testing by fantomas · · Score: 5, Interesting

    UK road signs were changed to their current style after testing in 1958, there's a nice summary on the BBC. This new mixed upper and lower case style became legally required on 01 January 1965.

      So yes indeed, typographical designers understood this in the UK quite a while before it was a widely discussed computer interface debate..

  11. Re:All part of their retro-COBOL strategy by alva_edison · · Score: 4, Interesting

    Part of GP's complaint is that he doesn't necessarily know or can discern the meaning of the symbols. Also, it took me roughly 20 minutes to find the icons on the title bar the first time I used 2007 because I was not expecting there to be icons on the title bar.

    --
    He effected a bored affect.
  12. Re:All part of their retro-COBOL strategy by amoeba1911 · · Score: 4, Interesting

    The ribbon bar in Office 2010 is the most unusable piece of crap ever. I had to memorize where all the stuff was before, now I have to re-memorize where all the stuff is because everything is in a new location that is not very intuitive.

    How hard is it to make an interface where I can just TYPE what I want to do? I want to type "line spacing" and have it bring me to the place where I change line spacing. Microsoft with their billions of dollars can't figure out how to do that? Is this a joke? So instead I have to press F1, type "line spacing" and have it show me the tips on how to do the special dance to get to where I want. In a world where the computer has 3 billion cycles per second I shouldn't have to waste my cycles trying to remember what awkward button sequence I have to perform to get the reward.