The official source of product insight from the Visual Studio Engineering Team
As we’re closing in on the final designs for Visual Studio 11 I want to thank you again for your feedback. I want to pass along that we are still internalizing your feedback and actively working on the next Visual Studio 11 milestones.
The purpose of this post is to follow up on a common request relating to the earlier RC preview post. The request was for more information on the Visual Studio 11 dark theme.
Leading up to our being engineering complete for RC we focused most of our design attention on optimizing the light theme experience, because that’s what our telemetry indicates the majority of you are currently using. Once that was complete, we turned our attention to the dark theme, focusing on the top dark theme feedback we heard from Visual Studio 11 beta. Many of you will see significant improvements to the dark theme in the RC release, but several of the key changes I’m sharing with you now didn’t make the timeline for RC. In this post, I’d like to share what you will see in RTM and call out some of the dark theme improvements we’ve made from beta to RC and subsequently to RTM.
As a part of giving you a preview of the dark theme I want to call your attention to several important characteristics of the Visual Studio 11 iconography. The first is that the icons are generally much simpler or more symbolic in their form. Secondly the color palette we employ within the icons has been simplified and made much more consistent.
In Visual Studio 11, we generate our icons from a common library of glyphs. This approach improves consistency as we produce the approximately 6000 icons of various sizes and formats that are used in approximately 28,000 different locations throughout the product. This presents an interesting challenge in terms of how to most effectively host these icons in different themes, and on different shaded backgrounds (tool windows, editors, drop-downs).
We considered the pros and cons of outputting separate complete sets of swappable icons for each theme. As we looked into this approach we found it still didn’t allow us to optimize across the various backgrounds on which the icons would be hosted in each theme.
In Beta and RC we used a ghost outline around the icons to make them visible on both lighter and darker backgrounds. The disadvantage of this approach is that it makes the icons appear fuzzy on both themes and too bright in the dark theme.
In the RTM version, we dynamically adjust the icons according to the theme, resulting in icons that are cleaner and better matched to the theme and background color. At runtime, we modify the luminosity of the raster images to match the outline of the icon with the background on which it is drawn and to make the fill and accent colors stand out effectively. For the dark theme, this essentially inverts the brightness of the icon, making dark areas of the original icon light and light areas of the original icon dark. The same happens on the light theme, as icons are displayed on differently shaded backgrounds. The luminosity match makes the background and outline of icons disappear as it matches the surface color they are displayed on.
The difference between the traditional outline based approach we used for beta and RC, and the approach we employee for RTM, is readily apparent in the following screenshots.
In addition to being simpler in form, and being better suited to dynamic theming, glyph style icons also lend themselves to much cleaner resizing or scaling. All of our Visual Studio 11 icons are maintained in an icon repository as vector graphic files which we output in various file formats and sizes as needed within our products. For example the same glyph can easily be rendered in a size and format appropriate for use in different Visual Studio 11 contexts such as the Solution Explorer or the New Project Dialog.
As a part of the Visual Studio 11 overall release plan we will be making all of the icons for this release available to you in multiple file formats including vector. You are free to take full advantage of the easy theme-ability and resize-ability of these assets within your own applications.
One of the most common requests for dark theme enhancements has been for us to theme scrollbars. As I hinted at previously we were close to sharing with you in our last post that scrollbars will be custom themed within both the light and dark themes. We’ve since completed sufficient testing to feel confident in sharing our RTM designs with you.
Visual Studio's UI is a mix of WPF, Windows Forms, Win32, HTML, and other UI technologies which made scrollbar theming a challenging project. Because there is no single technology solution to theming all scrollbars in VS, we applied scrollbar theming on a technology-by-technology basis. We created a style targeting ScrollBar and ScrollViewer in the root of VS document and tool windows. In some cases, where it’s not appropriate to show a themed scroll bar, the UI can opt-out. An example is a pop-up dialog that will continue to show light even in the dark theme should not show dark scroll bars.
Individual pieces of UI can opt-out of themed scrollbars by setting a special property on the HWND. UI may decide to opt-out if it is not optimized for the dark theme or if it presents a very specific user content.
The themed scrollbars are designed to work together with the RC changes we shared with you previously, such as drawing our own custom window chrome, to improve the overall sense of coherent styling within Visual Studio 11. As I mentioned above we would like to hear more regarding your impressions of the cumulative updates we’ve shared with you.
Many of you have expressed a preference for coding within a dark editor. For example, dark editor themes dominate the list of all-time favorites at web sites such as http://studiostyl.es/ which serve as a repository for different Visual Studio styles.
Chief among the reasons many of you have expressed for preferring dark backgrounds is the reduced strain placed on the eyes when staring at the screen for many hours. Many developers state that light text on a dark background is easier to read over longer periods of time than dark text on a light background.
Downloading styles from web sites such as Studio Styles provides a great starting point to begin customizations. With that in mind, we themed every single customizable item and category in the Fonts and Colors list to be consistent with the overall dark theme design. This way, further customizations can be made and new features introduced in Visual Studio 11 will benefit from the defined default dark fonts and colors. We made several dark editor theme updates in RC in keeping with beta and early RC user feedback, including:
In RTM you’ll also find that we have themed a core set of the commonly used dialogs. The New Project, New Web Site, Add New Item, Extension Manager, and Reference Manager dialogs now have dark theme versions of their UI.
For those of you who choose to work within the dark theme you will undoubtedly want us to continue to push our theming efforts deeper and more broadly across Visual Studio. We too are eager to continue our work in this area through the remainder of this release cycle and beyond.
I’ve included a screenshot that helps bring into focus how the various dark theme updates such as the shell, editor, design surfaces, etc. all fit together. The screenshot below shows a dark themed Visual Studio 11 with the Windows 8 simulator running in the foreground.
As was the case with the changes we announced as part of the previous RC preview post the RTM changes reflected in this post are designed to both address core feedback areas and to maintain alignment with our primary design objectives for the release. I’m hoping you will take the time to share your feedback on these newly announced RTM changes.
Monty Hammontree – Director of User Experience, Microsoft Developer Tools Division Short Bio: Monty has been at Microsoft for ten years focusing primarily on developer tool experiences. He and his team provide product design and user research direction for the Visual Studio product family. He has 25 years of industry experience in product design and user research management.
I'm curious: why rasterize the glyphs? I'd think that I would be interested to see benchmarks on the raster versions versus using the raw vectors as glyphs for all of the icons. It seems to me that using the vectors directly would be preferable (no need for size variants, and nice things like nicer DPI support and theming/color-changing/animation). WPF/XAML have a lot of vector art support baked in, and it would seem to me to be a good opportunity to use Visual Studio (and its huge number of glyphs) as a dogfood opportunity to make sure WPF/XAML's vector art support is the best and most performant it could be.
I find it inconsistent when some icons have colorful parts and some don't. I think you should stick with white/gray/black - just add more contrast and brightness like on far right in the picture. The only acceptable place for color is the code editor.
Oh and, get rid of ALL CAPS. Has anyone given you feedback that they want ALL CAPS? No. All the feedback is against ALL CAPS and it's wrong to assume that there is a silent majority hiding in the dungeons who want ALL CAPS.
There is still no contrast, just look at blogs.msdn.com/.../3716.01_5F00_RTM.png to see how everything just blends together, with the blue selection color really sticking out.
Also, REMOVE ALL CAPS FROM THE MENU BAR, IT LOOKS HORRIBLE AND UNPROFESSIONAL TO ANYONE WHO IS ON THE INTERNET SINCE ALL CAPS IS THE SIGN OF A 12 YEAR OLD (OR A LAWYER) TRYING TO GRAB ATTENTION.
1000+ Comments against all caps and now you ask for feedback on the dark theme? (which looks nice, by the way)
Why? If you don't listen, then why ask for feedback?
This is the third release with ALL CAPS in it - get those designers' hands off our beloved VS! VS isn't some toy project with a childish UI.
The icons need more color - one color for a part of each icon would look much better (including the explorer file icons!).
Can't thank you enough. Some of those colors in source code editors (C++, XAML) have been very difficult to get right. I'm looking forward to this!
What an improvement! I actually like the all-caps in the menu in this particular case.
@Max – Why do we rasterize the glyphs? The answer is pretty straight forward. Many complex vector paths don’t anti-alias well when rendered out into smaller icon formats such as our 16x16 variants. In such cases we have to go in and do what we refer to as “pixel-tweaking” for a significant portion of our icons in order to get them to look good at smaller sizes. The rasterized glyphs maintain the pixel level changes and allow the icons to appear clean and crisp at lower resolutions.
* Remove the all caps. How much more feedback do you need?!
* If there's some internal decree that you have to have all caps, allow us to auto-hide the menu; the way it works in IE. I rarely need to visit the menu so it doesn't need to stay there all the time.
* If you go the hide-the-menu route then we would need a way to add (a few) buttons to the top bar, next to "quick launch" (like save, run, stop, close all windows)
* The color used in "ready" bar seems too strong; use something closer to gray. The orange in debug mode is fine.
* Scrollbars look nice.
* Show us more icons in the solution explorer.
* The editor colors were better in the beta; in RC the white, blue, and green are too bright. It's that intense contrast (when working with a dark background) that tires the eyes.
It looks great. You had me scared for a moment with the beta, but now it's all good.
For one, it's not DARK, it's murky. Make the background BLACK, not puke gray. And remove ALL white background dialogs. HELLLOOO! You must have seen one or two unix APPS for way too short a time and copied their style all WRONG. Text needs to render clearly, which is not doable on the murkey background color. I know, designers don't know these things, but somebody there with some BALLS has to NO to this crapware.
(Yes, I KNOW it's way too late. Everyone here needs to know that none of the input here will change anything.)
"As we’re closing in on the final designs for Visual Studio 11 I want to thank you again for your feedback. I want to pass along that we are still internalizing your feedback and actively working on the next Visual Studio 11 milestones"
"The deadline is around the corner, we wont change a thing. We ROFL reading your feedback dudes coz we know better. Embrace THE METRO or die"
Thank you! I love dark themes but the way the icons looked in the Beta, I could not work like that and would of had to use the light theme.
Now that's been fixed, can you please fix up some windows so they use columns? E.g. The Find Results.
This is a drop-dead gorgeous UI. Really impressive and elegant solutions to icon and scrollbar problems. I have longed for a first-class dark theme since VS 2005. Thanks for investing so heavily in the dark theme; this is definitely going to make long hours in the office more pleasant. Great work, team!