Add some color to Visual Studio 2012
Usability studies have shown that both shape and color help to distinguis visual elements in a UI. The upcoming/current beta release of Visual Studio 2011 has removed color from the toolbars and from icons in e.g. the Solution Explorer.
Please make this optional so those of us that want a more accessible and user friendly IDE can have their cake and eat it too.
Please make more Color the the Visual Studio 2012. We must work with that black and white Studio. Colors help to find faster items. I don't know what Microsoft think about colors? Please give me my Color back!
I hate the chrome of the new Visual studio 2012. All toolbar icons are bitonal. Just blank and while not even grey shades in them and are tiny. I am having a hard time finding toolbar buttons. It look like i am back in early 1980s with bitonal computer screens. But this one is even worse than that. PLEASE BRING COLORS BACK!
revert to a more colorful theme so that screen elements are more easily differerentiated
Please bring back the colors in Solution Explorer. I am back to reading the words instead of quickly looking at the icons.
Have the UI designers of VS 2012 lost thier mind. Guys look at the UI, it looks so medicore that it seems older version than Visual Studio 1.1. I think VS 1.1 look and fill was better than VS 2012. Look at UI 2010. It was one of the best UI look and fill. How come quality of UI design degrades so sharply. I think designers of VS 2012 have lost theirs eyes. Folks go back to drawing board please.
Why microsoft is leaving the colorfull world? Some of the MS beauti doesnot require to change. You are making developer life so difficult with new IDE color theme.(I am sorry Black and white theme as there is no color.).
The User interface of VS2012 is ungly and black and white. Icons colors,location of toolbars all looks ungly.
I know in general if you want to teach someone color and picture is the best way to teach. but after seeing UI of VS2012 its hard to teach. I am feeling like I am a color blind.
Please do not change the nature.
I would like to add my voice to the list of those asking for color, at least as an option, to be brought back to Visual Studio. I understand the usability arguments that Microsoft is making, but it seems to me that you are overlooking one very important consideration. Many of us use autohide to solve this problem. Therefore, when we go into Solution Explorer (for example), we want our focus there, and the color schemes help us more quickly find what we need. Then, as soon as we click out of there, it is hidden and therefore cannot possibly distract us. Please don’t take this option away.
RC from Beta has a minor improvement, but its not enought!
The coloring is really almost not noticable, the problem was not with the status bar coloring, but with the items in the solution explorer and the ToolBox menu, and toolbars.
even in RC the files are not easily recognised!
and the all CAPS in the menu is really like watching Clipper from 1980 all over again!
guys please reconsider, METRO Style is NOT for an IDE developing tool!
you are making our lifes ******, and eventually we will stop folowing the .NET.
PLEASE!!!!!! Switch to a sane color scheme who ever had the idea to remove colors and contrast have him tared and feathered!!!
and sent to Siberia!
this color schema is painfull to look at and debilitating..
it will reduce productivity and programmers will to live!
even cats and dogs would complain and they only see a few more cholors the monocrome...
the human eye in contrast can see as much as 10 milion colors why should we be limited to gray scale?!!
I wont be upgrading my visual studio 10 if these colors remain that a absolute iron hard fact...
If your adding a theme editor to it and this is your way of forcing the comunity to find the optimal color theme by giving them a kick in the @$$ then by all means... but i seriously hope your not expecting anyone to work like this...
that would be insanity!
Removing color from icons and symbols in Visual Studio is a step in the wrong direction. What is the use of icons and symbols? They have to make functions recognizable. The more icons you have the more they have to be well recognizable.
Another aspect: the use of color makes Visual Studio friendlier. The actual beta looks gloomy and sad
Updated Status: 7/2/2013
Thanks to everyone who voted and commented on this issue. Visual Studio 2013 has increased color and contrast use within the user interface while continuing to focus on giving the content you are creating and editing visual prominence. We’ve utilized the feedback you gave us to help refine our approach to color and contrast within three main areas: 1) we added color to icons and reduced line weights to improve icon scan-ability and to better communicate icon meaning and categorization; 2) we added line work and raised contrast levels to increase visual separation between screen regions; 3) we included a built-in “Blue” theme option at product first launch to better support user choice.
In keeping with these three areas we have made many changes to the Visual Studio 2013 built-in themes. In high utilization and icon intensive areas of the product, such as common toolbar actions and code hierarchy elements, we refined the color and/or line weight of over 1,000 commonly used icons resulting in color being applied to ~80% of standard and debug toolbar icons, ~75% of code hierarchy icons, and 100% of active notifications. In both the Light and Dark themes we increased contrast levels and introduced more border line work to better highlight the edges of content areas such as input fields, tool window borders, active selection states, etc. We also introduced the ability to choose the theme that best meets your preferences and work environment needs as a part of the product first launch experience.
Many of the changes we’ve made are subtle in nature but broad reaching in their application. As Visual Studio 2013 Preview has now shipped, we’re closing this item to give your votes back for you to use on emerging topics. We encourage you to try out the changes we’ve made and then share additional feedback you might have.
Visual Studio UX Team
Take a look at the VS 2012 Color Theme Editor – it is an option for creating and editing your own Visual Studio themes.
Doug Turnure – Visual Studio PM
The color theme editor can not recreate the vs2010 look and feel and thats what people want back!
Why tool for qualified engineers got interface for housewives?
This is a developer tool, please don't confuse it with Office and other end-user products (what should NOT be monochrome either!).
And use Windows colour scheme what the user selects, don't ignore it!
Ugliest and useless interface ever .. It looks like its missing colors icons and so on, I first through did I miss something in the installation or do I need to take some acids to see colors in it ?! .. There are people out there working with this tool please come back to what it was in 2010 or even better 2008 .. Talking about consistency Office 2013 has at least colors to for its icon why not visual studio ?
Dudes we are in 2012 soon 2013 and not in the 80s with an old mac! I guess we will unfortunately have to revert back to 2010 as is its not possible to work more than 1 hour as it is. What a shame ...
Andrew W commented
Thanks for the theme editor.
A suggestion folks - use the theme editor but after your selection you need to re-import your colour/font settings from vs2010 as these are reset by the theme editor. This helped me.
Still need to re-learn icons. They were perfect in vs2010, we knew them, we loved them so why oh why change them who had that as a metric? - Looking at the new ones while some may actually make more sense, the comment/uncomment icons for example this is not the point, the old ones are imprinted.
With all due respect designers need to learn to step aside sometimes.
Mark Sowul commented
QFT, on the issue of (pointless) consistency:
"While the Visual Studio 2010 visual appearance is unique, it does follow the Microsoft Windows UX guidelines. Microsoft does not use one standard visual appearance for all its products for multiple reasons, including:
• Not every product has the same users and therefore the same UI is not appropriate everywhere
• Microsoft has such a wide range of products, it would be impossible to do one visual appearance that is a "one size fits all." For example, it would be virtually impossible to use a single UI design for Zune, XBox, Visual Studio and Bing.
• Different visual appearance of different products helps differentiate/brand them.
• Having a single UI appearance would not give individual products flexibility to evolve as needed in response to trends, customer and business needs.
If there are specific aspects of the Visual Studio 2010 UI that you find hinder the usability, I encourage you to follow up with these details.
Suzanne Hansen, Program Manager, Visual Studio Platform Shell Team"
(See how many people complained about VS 2010, a whole 11 of them...versus 17 downvotes)
What happened to her?
Stop drug abuse among UI designers!
I had a thought where this new "direction" in user interfaces (Visual Studio, Office, MapPoint, Windows 8) might have come from...
It all comes from when the people who grew up watching "Sponge Bob Square Pants" and "Ren & Stimpy" learned to accept those cartoons as the "state of art" for computer graphics.
They have now grown up and become the ones who make the decisions as to what goes into the new generation product user interfaces.
VS 2010 had something like "Finding Nemo" graphics; VS 2012 now has "Sponge Bob" graphics. The problem is that most of us grew up on "Finding Nemo" quality stuff. Our expectations just got too high - yeah - that's the problem.
I hope I've not been too abstract...
Developer Art commented
I have been reading all those infuriated comments since the beginning of the year. I was doubtful what to make out of it. Finally I succumbed to my curiosity and decided to give the thing a try. So I just downloaded and installed an Express edition. Well...
In about 7 minutes my eyes started to ache from the "light" theme. I went to the menu and switched to the "dark" theme. Well...
It's not usable either. The problem is too much contrast from very bright text on a dark background. It blurs in my eyes. It's an absolute no-go. The text should be softened otherwise it pops out and distracts you from the content. You see bright letters and bright lines but you lose the focus on your work.
Therefore neither light nor dark theme are usable. Frankly I'm at a loss. Is that an innovation over VS 2010 design? It reminds me of the old MS-DOS days where there was a black screen with bright letters on it. I suppose I could take it upon myself to put up my own theme but I don't have neither time nor inclination to spend my precious time on something which should work out of the box.
Furthermore all monochrome icons make it indeed very difficult to distinguish elements quickly. They look great when you dwell on them and meditate. But they don't work if you attempt to use them.
What I also don't understand why when most of the icons are monochrome there are still very bright and colorful icons now and then. Forgot to replace them?
VS 2010 was elegant, stylish, intellectual.
VS 2012 is coarse and brutal.
Take it from a programmer with an eye for design and usability (or a designer with a thing for programming) - VS 2012 design is unfortunate with very low usability. It must be fixed. And given that just about everything about it is unfortunate the wisest course of action would be to reverse to 2010 design and continue to inject little improvements now and then where they make sense and the community votes up. The 2012 should be discarded completely.
I think I will be staying with 2010 for the time being. I can live with it for a few more years without a problem.
I done with visual studio - **** themes. the whole thing is ******* slow. i am switching to developing using sublime text and using build scripts **** you visual studio even if it means losing intellisense and otehr ****
Rick C. Hodgin commented
@Phil, hadn't thought of that. Well, as another poster said... "Eclipse is even starting to look inviting, and that's saying something..." Just about true.
Macintosh icons eventually became full-color after ~15 years. Are MS going to repeat evolution of Macintosh, and we must wait same 15 years till UI come back into sanity?
Phil Murray commented
@Rick, Knowing M$ that would violate the EULA
@Rick C. Hodgin:
Please take a look at this http://vsip.codeplex.com/
It works like a charm but there are still uncovered areas, like the most used Toolbars and some of the lesser used Toolbox icons.
Would be awesome if the community could get together to fix the biggest flaw in VS2012 together, since MS is intent on degrading our productivity.
Rick C. Hodgin commented
There is a manual workaround for this. Using the information on this page (http://www.codeproject.com/Articles/3087/Reading-and-Using-Resources-in-an-Executable-file) we can go through every EXE and DLL that came with visual studio 2012, Enumerate all of the resources within, find all the things which are icons used by Visual Studio 2012, group all of them which look identically into a category, compare that with what we see on screen, then go through each of those instances and replace them across the board.
I'm half tempted to write an application to do this.
Icons still suck and apparently Microsoft has no plans of addressing this, they wrote:
"We currently have no plans to offer the old-style icons for Visual Studio 2012."
"We believe this design consistency is important, and we expect the icon styles to become familiar and comfortable over time."
So go here and tell them what you really think:
Simeon Albertson commented
Please vote for icon colors when it comes to identifying folders! It's also very important: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3307998-allow-humans-to-differentiate-between-files-and-fo
Some r******d Macintosh1984-f**s are trashing our VS.
I think I use a ms-dos program. I never upgrade to 2012!
"Build a system that even a fool can use, and only a fool will use it."(c)