Menu
We have seen that office has the ribbon UI since 2007. Now is 2010 and we all feel the great productivity the ribbon has brought to us.
My question is why Visual Studio, now 2010, still not use the ribbon? What do you think? Please share.
382
To add a toolbar, choose the New button, specify a name for the toolbar that you want to add, and then choose the OK button. To remove a custom toolbar, choose it in the Toolbars list, and then choose the Delete button. You can delete toolbars that you create but not default toolbars.
Follow these steps: Press Alt to make menu visible. Click on the View menu, navigate to the Appearance option and choose Show Menu Bar.
Go to VSCode settings ( CTRL+, or CMD+, ) and search for shortcut menu bar . Toggle buttons from there.
Ribbon its a great user interface to organize tools like buttons and some kind of small items. But it doesn't work well, (or at least it's very difficult to achive) when the user interface has to be very personalizable as Visual Studio has to be. And there's also the problem of many windows that are not toolbars, like the solution explorer or the many different designer, they can't be placed very easily.
Whili I'm not saying it's impossible. There is a lot of features that would have to be rebuilt to accomodate a ribbon.
From MSDN Ribbon User Experience Guidelines
Command scale
Is there a large number of commands? Would using a ribbon require more than seven core tabs? Would users constantly have to change tabs to perform common tasks? If so, using toolbars (which don't require changing tabs) and palette windows (which may require changing tabs, but there can be several open at a time) might be a more efficient choice.
For efficiency and flexibility, do users need to make significant changes to the command presentation contents, location, or size? If so, customizable and extensible toolbars and palette windows are a better choice. Note that some types of toolbars can be undocked to become palette windows, and palette windows can be moved, resized, and customized.
Because of some of this reasons I believe Visual Studio works better in a toolbar-based interface
PS: While I don't believe Visual Studio will implement the ribbon, Autodesk products like AutoCAD are very good examples of very complex ribbon-based application.
52
I kind of think Ribbon would be as bad for Visual Studio as those silly button bars. Working quickly in visual studio is all about good navigational keyboard shortcuts, not mouse clicking.
36
I have been using Office 2007 for over a year now. The answer is simple, the ribbon interface is an almost purely cosmetic addition that in fact still slows me down dramatically.
It looks cool, and I like the fact it has more "text" and larger icons from a "Learning" perspective. But after you have "Learned" an interface the ribbon gets in the way. I find the excessively "verbose" text is distracting and causes me to spend more time looking for the desireable command.
Effectively it is just a menu turned inside out and sideways that causes you to have to click far too many times to perform actions. additionally the layout is very unnatural, it begins at the top then switches to the bottom "chunks" then goes into random left to right and top to bottom sections with possible sub menus.
This statement in the original post to me is completely inaccurate.
... Now is 2010 and we all feel the great productivity the ribbon has brought to us ...
I end up putting ALL the commands I normally use on the quick access toolbar and "hide" the ribbon to make up for the screen real estate it steals.
If it was put in VS I would do the same thing, add all the common commands to the quick access toolbar and "Hide" the ribbon.
32
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
