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
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
Chris Lively commented
If this is anything like what metro is going to be like, I may just have to finally take a look at linux. There are no words to properly convey the amount of disappointment I am feeling right now with regards to this product.
We have a commercially available software package. It has plenty of color. Our competitors stuck with the old grey ****. We outsell ALL of our other competitors combined. Know why? Because the **** thing looks good. Period.
This looks likes ****.
Chris Lively commented
Just installed VS2012. Very disappointed. "light"/"dark" are the only options? Seriously? Is the usability team color blind? I remember the old monochrome days... they weren't fun.
I haven't downloaded VS2012RTM yet, so did they change anything regarding the UI or is it still running a maximum suckage?
James Stewart commented
I can not see why the appearance of the development tools (VS) should have anything to do with the current trend in the appearance of applications. Does the appearance of a lathe or drill matter when creating a new stylish widget? What is vital with tools is practicality in the development context only; a developer/lathe-operator can create any style the market happens to want; a new consumer style trend does not require a new style of lathe.
Paul Callaghan -
<I have found that using the quick launch as my 'go-to' for finding commands instead of the 'old user interaction' of hunting for the menu item until I train myself to use the keyboard short-cut has enlightened me to how the new design is supposed to work (from a user's perspective).>
This is really a very stupid design as it requires one to be familar with the commands - its like retro to Unix. It requires lots of practice and expreince to use. Menus and icons are an aide memoire - and thats one of the reasons Windows 8 is going to suck with the average user.
Nothing wrong with it as an option but its should not be the primary selection method.
Microsoft is being arrogant and stupid and at the same time here!
>They are not as important because when I start typing 'new' in the quick launch my options are suddenly recuced
Main menu is not important. It is only several dozens items on constant places. Important are solution explorer with 100500 items, changing every day. Also intellisense, search results, and other user data.
Of course, this has meaning only for those who work with projects more complex than hello-world.
Paul Callaghan commented
There have been many comments about the lack of color in the UI. I think that the disconnect between the developer (microsoft) and the user (us developers) is that they were hoping everyone would catch-on to the whole 'quick launch' concept.
I have found that using the quick launch as my 'go-to' for finding commands instead of the 'old user interaction' of hunting for the menu item until I train myself to use the keyboard short-cut has enlightened me to how the new design is supposed to work (from a user's perspective).
I now see why 'Once Important UI Elements' such as colorful icons are being deemphasized. They are not as important because when I start typing 'new' in the quick launch my options are suddenly recuced to a nice, small, list and the icon color becomes meaningless.
These bright (as 1000 suns) white edges and almost-no-visible separation lines between zones very strain eyes. Can't work longer than 20min.
Visual Studio is MS's most important product. Every other product in MS's portfolio depends to some extent on Visual Studio.
Why they would jeopardise their entire company by so utterly screwing this up and alienating their customers, I don't know. Seems like commercial suicide to me.
No doubt this will open the door to competitors though. And perhaps this cloud may have a silver lining, if other quality IDEs emerge to take on VS (I could probably design a better looking IDE, and I'm a programmer).
Look what happened with IE, MS got lazy and arrogant, next thing you know Chrome is the market leader and IE is pretty much dead and buried. I would love to see Google come out with a c# (or equivalent) IDE, done right from scratch (without all the legacy that seems to be forever holding VS back).
Will be exciting times. But I won't be embracing VS 2012/Win 8.
>losing market share
Visual studio exists not mainly for profit (it's main role is to promote windows, sql server, etc). Some "effective managers" want to cancel this project (to get bonuses for reduction of costs), and they need to display it as non-popular among users. This is easily achieved by disfigure UI.
I've made a few comments on this issue, but I'd like to make one more now that I understand Microsoft have released VS to manufacturing on 1st August.
Microsoft have ignored the substantial negative user feedback regarding the colourless and SHOUTING UI.
The Internet and particularly facilities like User Voice provide a fantastic forum for giving an receiving customer feedback. Modern and successful corporations embrace this opportunity for dialogue with their customers and act upon it accordingly. The old adage "the customer is always right" still holds true, the market is consumer driven.
Many VS users have spent time and energy providing Microsoft with feedback on this issue not only so that they get the product they want, but also to help Microsoft itself make a better and more successful product.
For Microsoft to completely ignore that feedback displays an arrogance and contempt for their customers which even for an organisation of their size is extremely dangerous. Even large corporations can ill-afford to ignore/insult their customers now that we are all so connected and views/recommendations are so easily shared.
There is strong competition now for Microsoft in all areas of even their core businesses and their attitude, such as that displayed over the changes to VS, is the first step in losing market share.
radioman . lt commented
..hey it's me again, just wanna say few things about boring gray colors: it's F_U_C_K_I_N - FAILURE ;}~
>I cannot work
it was their goal
I want totally colors back !
Make options for those who like gray scheme. I cannot work without colors :(
Christian Hawkins commented
Please do yourselves a favor and fire the genius at the top that pushed this idea through.
Christian Hawkins commented
With these horrid, low contrast, colorless icons, Source Control Explorer in the Dark theme is about as unusable as it gets.
Seriously - ditch the WHOLE thing. Just give us the new functionality, keep the Metro or whatever you call this carp.
Consider that the ASP.Net MVC developer does not even use the GUI designers but instead relies heavily on numerous files scattered in solution explorer. So what does MS do? It makes stuff gray supposedly to focus the eye on the GUI designers and botches the solution explorer - exactly the opposite from the MVC developers' priorities.
I bring up MVC is because most of MS development jobs are ASP.Net. So what MS is doing here is truly incompetent.
"the new outlook.com is similarly grey"
I saw that as well and provided some feedback (like their going to listen right??) to them effectively telling them the lack of color and contrast issues make it unenjoyable to use. Just when Hotmail was starting to look pretty good, they launch the outlook.com UI. I think Microsoft is either going to win big time, or more likely, lose huge marketshare fast. Across the board the UIs are getting sucky. They oversimplified to the point of it being more effort to use. Now I'm just waiting for that 'DECLINED' email to pop up regarding the VS2010 theme request. I will be floored if they actually listened to us and provide the option for a full VS2010 theme. Imagine that...
Incidentally, I see the new outlook.com is similarly grey, so apparently the colourless format is a company wide policy rather than a Visual Studio thing. So it seems the UI designers of VS had their hands tied all along.
The extremely odd decision to ignore the use of colour as a visual/navigational aid is NOT so that VS users can focus better on the code as Microsoft claimed but is actually a company wide policy which effectively destroys any enjoyment in the use of Microsoft products.
It seems to fly in the face of both common sense as well as business strategy. Very Strange.
"It definitely was made with intention to drive out users from VS to some other product... But to which?"
Sharp Develop http://www.icsharpcode.net/OpenSource/SD/ has quite a lot going for it (including a UI that doesn't force you into becoming manic depressive)