Incorporate the ribbon and ditch the toolbars!
Is there any other app that has an incredible amount of commands that would benefit more from a results-driven UI? I think incorporating the ribbon is a no brainer!
We appreciate the feedback about the complexities of the command systems in Visual Studio. We are currently evaluating improvements we can make in upcoming releases.
In the next few months, we are contacting users that are interested in this topic to get detailed feedback and evaluate possible solutions. If you are interested, please sign-up here (https://visualstudio.typeform.com/to/YNvqVk).
Program Manager – Visual Studio IDE
How do I use the link? I have created a account on the site, but what do I do now?
Stefán Jökull Sigurðarson commented
The signup link doesn't work.
With regard to the previous comment, it is *good* that “windows jump around, depending on whether you are in debug mode or not”. I have different priorities for information on the screen while debugging, but rearranging things by hand when I start/stop the debugger would be barely practicable. Optionally having the same layout would, of course, be fine.
But I still do not think that the ribbon makes it easier to find functionality, and why should I learn a visual language when I am quite good at the approximation to English used in the menus?
Everything is better than the current messy GUI.
Menus and windows jumps around, depending on whether you are in debug mode or not. It is quite impossible to find anything in the menus if you do not know where to look. There are lot of windows that do roughly the same thing, but not quite.
From the beginning, the user interface was amazing. However, many new features have been added and changed, and the user would need a hefty cleaning and redesign today.
Kirill Illenseer commented
Would be great. The ribbon helped me in Office finding functions and yeah, VS is a functionality monster, more so than Word.
Please MS do NOT introduce the ribbon clutter, at least not unless there is a full option to use toolbars.
For those complaining about screen space:
The ribbon in Office 2007 etc. is collapsible.
So if VS incorporates the ribbon and you collapse it, you'll probably end up with *more* screen space than you have now, not less.
Fernando A. Gómez F. commented
I'm all for the ribbon. VS has lots of commands hard to find. For example, searching in the menu for a specific Window can be a pain (is it in Edit menu, or in Debug menu? Plus, they're not sorted alphabetically, the pain!). And as stated, Vs would benefit from this UI.
As for the screen space, with modern displays it really doesn't take that much space. My Word uses 1/5 of the space. However, VS supports multiple monitors quite well, so there you go. Additionally, Office 2013's ribbon comes with a li'l arrow that would minimize the Ribbon. If you want to save space, just minimize the Ribbon and keep your common toolbar menus in the Ribbon's QAT. Finally, you can always Alt+Shift+Enter and go full screen.
There's no excuse for not having a Ribbon interface, IMO.
NO! NO!! NO!!! (At least not compulsory) The ribbon is fine for people who want to devote a quarter of the screen to a facility for exploring a UI/functionality they don’t know, but I am far happier with well structured menus for the same job.
Actually, I wouldn’t object to an optional Ribbon, but I hate compulsory ribbons. I go through both ribbons and menus with keystrokes a lot of the time anyway, and I would get really little benefit.
I think that incorporating the ribbon interface in Microsoft Office and other "common user" programs was a good idea because those programs are easy to work with with drop-down menus, and are even easier to handle when using the ribbon interface. Visual Studio however, being a developers' software, is much more complex. Using the drop-down menus, it's easier to sort things out, and you can compact lots of options into very little space. Can you imagine how hectic things would be if Visual Studio switch to the ribbon, and suddenly you had to move your mouse further to click on something you could easily have appear next to a sub-level in the tool-bar? It is because of this that I think Microsoft should leave the option of drop-downs or ribbons up to the user.
Another Ignored Customer commented
Nice to see someone still has a sense of humor - I guess the OP hasn't used VS2012 yet.
I resent the implication that because I want a Ribbon and I use a mouse and menus instead of a key board that I am not a "Power User" I am most certainly a Power user. I just happen to be a very visual person, I don't remember arbitrary commands very well but I do remember visual cues really well. As for those suggesting that I should spend time configuring the tool bar, you are missing the point. I am a Power user therefore I need a visual way of navigating to every command available in Visual studio.
I would love to use VS with ribbon.
Since VS is all about extensibility perhaps the part that takes care of the menu/toolbars could be an extensible part where we could have an option between menu/toolbars and ribbon. It could be incorporated on the themes part so I could choose a theme that uses ribbon while ribbon haters could choose a theme with menu/toolbars.
Cavan Watson commented
@Noel... I've thought for a long time that 'Context Menu' is the most outstanding misnomer. I'm not totally convinced that its Visual Studio's fault. Both Reshaper and Code Maid, just assume you'll be using their extensions in all contexts, so place commands on the global VS Context Popup... I'll have to have a look at the extension mechanisms to clarify.
Come on haters, there is no reason that you will loose any keyboard short cuts, because we get a ribbon interface. for those that want extra room then collapse the ribbon (or buy a larger monitor).
Its not the tool bars that need addressing it is the context menu. With resharper and a couple of other plugins like VS commands and Code Maid my right click menu is out of control. Help!!
I find it funny that MS in their pursuit of standardizing the Win8 look across their programs failed to standardize the menuing system used.
The three main Microsoft applications I use are IE, VS and Office. All have different ways of presenting menu type selections.
Out of those, the Office menu is the most accessible. VS's is close with the tiny toolbars; and IEs is, well, looks like they just threw a lot of commands into a corner.
If you are going to standardize the color scheme, then it seems like you'd want to standardize the whole enchilada.
Jens Melgaard commented
It's funny to see how many hates the ribbons... They are a drop-in replacements for the Menus, not the toolbar and can be easily collapsed to nothing.... So I would vote for the ribbon to replace the horrible tree structure menus VS has...
In the end, I so rarely use menus and I haven't used the toolbars since VS2008... So anything I con hide faster than the toolbars is welcome.
Sergey Chubukov commented
I'm strongly against this. I cannot express how much I hate the ribbon interface, nor do I know a single developer who likes it. Its forced introduction in MS Office products was a disgrace.
Good idea, the keyboard shortcuts in the ribbon really work well. To all the ribbon haters, you can hide most of it by just double clicking the "tab" area.
I'd love the ribbon interface in VS!