Add an optional configurable toolbar below the menu #41309
Comments
show me other popular ide without toolbar
vijayvepa opened this issue on 4 Dec 2017 15:34
Yep! Without vscode :) |
|
Because #18042 has been closed, I've switched to another IDE. Sorry, Microsoft! |
|
Sadly I don't think Microsoft or vscode team cares what customers want. This topic had long been almost conspiracy levels of blatant ignoring countless issues. I too took the notifications as someone on the team who looks on vscode as their baby... Seeing it working their way with no interest to the contrary what so ever. I've purchased jet brains full subscription and haven't looked back. I'd love vscode to be in my tool box... As a software engineer seeing this sort of feedback to community suggestion.. it just left a real read bad taste in my mouth. Vscode team won't care they lost a handfull more users... So it is what it is. |
bpasero
changed the title
bpasero
added
feature-request
|
I totally agree with OP. The biggest feature gap by far in VSCode is a missing toolbar. I want an old school ms-office-2003-like toolbar, with toolbars and toolbar buttons. Thoughtful icons, and mouseover to see description and keymap alternates. There should be good default toolbars and they should be customizable by the user. Plugins should be able to define plug-in specific toolbars as well. A toolbar will drive a lot more adoption and will make it easier for users to learn the keyboard alternates. I am a long-time Visual Studio, eclipse, and Jetbrains user. I just spent a lot of time setting up and learning VSCode, and I can say VSCode is great except for the missing toolbar. If it had an office-like toolbar I would switch to VSCode exclusively. But without it I'm afraid I will have to go back to Jetbrains. Microsoft, please stop sabotaging your own future. |
|
a temporal solution can be using the status bar to add the commands you need. and this one can add tasks to the status bar: result:
|
|
I'm with @morozovsk and @MikeSummit on this. vs code has so much going for it however lack of feature discoverability, lack of easy navigation and forcing users into a land of Ctrl+Shift+P / the command palette bucket of everything does hold it back IMO. Toolbars are a must have feature that vs code doesn't have. Do the right thing. Implement the user interface that is a globally accepted standard in user interface design. Make vs code really usable with default toolbars, plugin specific toolbars and user definable customizable toolbars. I'm sure this will be a large feature to implement however that should not prevent this feature request getting visibility on the roadmap. |
|
@alkorsan Please add mine to your list, which provides a good feature to include in a toolbar ... Devs should have the option to add a clickable button for each of their tasks. https://marketplace.visualstudio.com/items?itemName=GuardRex.status-bar-tasks I'd love to RETIRE that! |
|
Coming from Atom, a customisable toolbar is one of the features I miss the most. I'd rather not have to learn new shortcuts since I should be focusing on the actual code. I hope we get something in the near future! Keep up the great work, Microsoft. |
|
Interestingly this issue has not been closed as out of scope yet and I remain hopeful that this feature will be implemented. The official 2018 roadmap does talk about "Happy Coding", "we want to make the experience even more pleasant, for both new and existing users" and "eliminate blockers that make it hard for people to adopt VS Code" so without specifically saying that this issue is on the roadmap, it should be on the roadmap and being worked on based on what has been said. @bpasero has been active in this issue and he is an active VSCode developer. It would be really nice if a Microsoft VSCode team developer could find the time to go on the record in this issue and say what the plan is. |
|
Haven't they gone on record and said it's basically not gonna happen for the foreseeable future? That seems like what I understand with all the open and closed issues and stating it's not even just gonna get stuck in the backlog... But more like "not interested" even though the issue has been brought up countless times. Not trying to start a negative feedback loop or anything... But this topic is a sore one... And I almost feel like there is conspiracy level of anti-toolbar. Someone somewhere decided no amount of feature requests for it will ever result in a general purpose toolbar... And their mind is made |
|
Hi @ronnyek I've seen multiple closed issues similar to this one and I do understand where you're coming from with your stance. I'm trying to stay positive. The fact this issue remains open today gives me hope that there's willingness in the vscode team to consider that this really is a valid suggestion. I also hope that I'm not deluded :) I'm happy to repeat that the lack of default toolbars, plugin specific toolbars and user definable customizable toolbars are a real barrier to entry / adoption of vscode for new users and this missing feature is a also and endless productivity inhibitor for those people that are willing to stick with vscode regardless. |
|
oh yeah, don't get me wrong... I'm for this change, and like I said I don't want to be a negative feedback loop or anything... Just surprised this issue has stood as long as it has. VS Code is making leaps and bounds as it progresses... and just really really dont understand the opposition to the toolbar. For now I've written off vscode for front end editing in favor of webstorm, but I'd love to have vscode as an option in the future |
|
Seems so basic, I was very surprised when I didn't find one ... but I guess if the designers have a philosophy of keeping a very minimal UI maybe they feel its not worth the effort to support one |
|
maybe anyone can try to port this atom toolbar extension https://github.com/suda/tool-bar |
|
I started a feature branch with some code that aims to do that fixed toolbar: There is much work to be done yet. |
|
@junalmeida hi, currently this feature request (as many others) is open so we can gather more feedback from users, not because we want to tackle it right away. As with all feature requests the best first step is to usualy start a discussion and not start coding right away. Kind regards |
|
@isidorn notepad++ is a super minimalstic code editor:
vscode is a ... vim way code editor. a mouse was invented in 1946 but you force us to use the keyboard. If you want your program to be used along with others you must be compatible. If you don't want to be compatible (ms way), you can do as you want but don't pretend that you care. 😠 |
|
@isidorn I got your point but I guess that a discussion was already started here in this topic and others. Anyway, I started coding this as a POC for myself, trying to understand all the guidelines used and the UI code. If this is not the direction of the official VSCode team, no problem, but this is the beautiful of open source: anyone can fork and do experimentation, and this does not necessarily mean that a PR will be accepted. ;) |
|
This is a really weird decision and will definitely be a big blocker for me personally to adopt vscode (and I imagine many other users, too) |
|
Also due to lack of toolbar everything gets dumped on the status bar. There are extensions that clutter the status bar very badly like git-history, cmake. Since you cannot disable status-bar icons individually, there is not space for rather important things. |
Or just compare thumbs up/down which gives less than a 10% of audience against this
|
@netizen-ais less than 10% of audience against what? |
|
I've asked similar question on StackOverflow (with the crosslink to this post). Maybe someone could elaborate on this. |
|
I proposed this as a feature add for Fleet... see if jetbrains community is more or less receptive than the vscode dev community is. |
|
@ronnyek Unfortunately, Fleet is not Open Source or Free Software, right? |
|
I dont think JetBrains has ruled that out (I seem to recall Q/A about fleet, and they basically said they haven't decided) for fleet... but its possible it ends up closed. Regardless that doesn't help people wanting to use VSCODE with toolbars |
|
the toolbar is useful, for example, the current debug tool is floating and can cover the content of the editor. Putting it into the toolbar is the best solution.
|
|
@xinatcg What is that toolbar and how can we use it? Or better, how can we use it for commands added by extensions? But I don't consider "overlapping the editor" a good thing. After all, it will be in the way when you want to access the covered parts of the editor. Browsing the beginning and end of this issue (what GitHub showed to me), I reinforce my doubts that Microsoft (or whoever runs this project) is actually competent to do so. The team seems to add stuff that may or may not be useful to very few people, and stubbornly ignores users who wish for UI improvements of all kinds. It feels like it was never planned to release VSCode to the public and deal with foreign users. VSCode is the weirdest software I've ever seen: It has the most potential to become the best universal code editor but at the same time it's the most comprehensive collection of missing essential features for a code editor. Has somebody already suggested forking this project, giving it a proper name that doesn't confuse every second web search with an older similarly-named IDE, and add all those essentials like this one? |
|
Any updates? |
I don't think there is any problem with competence... what code does do is impressive, and is a fairly good user experience... its a matter of the governance of the project. "Let's allow this that and the other thing... but we dont like toolbars so we'll just passively ignore any and all efforts or requests to do so"
There are several forks of code, but everything I've seen so far, tends to follow code in this way. Infact they tend to keep ui and code as close to code as possible, and decided to fork code for... unknown reasons? What's more disappointing is that "all new" ide's or "code editors" are springing up, copying vscode in a lot of their user experience decisions, which I think is a huge mistake. (fleet appears to have massive potential, but already copying some of what I see has vs codes biggest shortcomings =( ) |
|
300+ likes and 4-5 years since this has been opened. Incredible how long a company can ignore it's user base... pretty stupid imo... Is that an elitism issue where the core dev team of the product just are dead set on their ideologies? |
Oh, maybe the dev team don't use VsCode (because the lack of toolbar), so they don't understand users 😃 |
I really hate that one, tbh. It is literally ALWAYS in the way of something, constantly moving that around. I would love to stop playing "Debug Bar Simulator".... |
|
Another year I'm still seeing this pop up in email notifications.. everytime I see a vscode changelog I just wonder how in the fuck can this company implement anything but what so many are asking for. |
|
I'm trialing VS code at the moment. When I click on a CMake Preset at the bottom of the window, it brings up a menu at the top of the window. This is surely a bug and not acceptable UI behaviour? The point is, this would be improved if we could have that toolbar, or configurable elements of it at the top. Then at least when you click on one of these extension buttons to bring up the command palette it would be closer to it. However, in my opinion, it still wouldn't be as good as a dedicated CMake Preset menu which when clicked on just acts as a normal selection box for choosing the preset, rather than a shortcut to the command palette. Personally I think the command palette seems like a cheap way of providing all functionality in one go, but from a usability perspective, having come from Xcode, MSVC, and CLion, it's awful and I won't be continuing with VS Code until CMake integration is more user friendly for projects with multiple presets and targets. All I want is some nice clean menus at the top to select the current Preset, the current Target, and a Build menu to Clean/Rebuild/Install in various scopes (current preset/target, current preset/all targets, all presets/targets). Neither this or CLion can do this. CLion comes closer, but has a dreadful search/find functionality with all these annoying and fiddly pop-ups and so forth, whereas VSCode is much closer to Xcode's, with the ever-present search side panel, which I prefer. I also prefer the feel of VS Code editing, again, it's more like I'm used to with Xcode. Still searching for the ultimate CMake/C++ IDE... |
|
There isn't much point in this thread anymore. The powers that be aren't interested in making VS Code more accessible or listening to the users. You can tell by the lack of any movement after 5 years. |
|
Actually having discovered the CMake Project Status option, hidden away in the settings this gives me much of what I need in the sidebar for choosing configuration/build presets. |
|
And here is another perfectly reasonable request about a basic feature that serious code editors have had for ages being ignored since forever. The day this project loses steam the debacle will be really fast. |
|
I'm being forced to use VS Code and now I see this... this is so typical of Microsoft PMs. "We need to get feedback on something that is easily understood, already proven in concept, requested by customers and optional to use. Maybe next decade." |
|
Its not even that... it's the whole massive demand for this, and the conspiracy theorist level (I know how crazy this sounds) of ignoring feedback. Consensus from ms/vscode team seems to be "vscode is an enhanced text editor, not an IDE" until you need plugins for every last little framework, developing against some random obscure hardware, etc etc etc.. I've all but given up hope on this topic, don't think its gonna change (even if hundreds of thousands of people showed interest or asked for this.. .it seems to have been decided, and I'm skeptical it'll be reconsidered). I'm all about supporting competition at this point. |
|
Just a reminder to celebrate 6 y.o. issue soon. |
|
they are... retarded |
|
They think that CTRL-SHIFT-P and CTRL-O are easier...
…On Wed, Nov 1, 2023 at 6:50 PM XeonG ***@***.***> wrote:
they are... retarded
—
Reply to this email directly, view it on GitHub
<#41309 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABHCCPEGUN5MWVGIPRB2HLYCKDYBAVCNFSM4EK3PIJKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZYHEZTSNRTGQ3A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Still waiting ... |
|
I need custom buttons as well, but once I went to the trouble of adding my task to the status bar with the status bar command extension, I was "fine". I do wish VS Code would not need an extension to do this...Right clicking on the status bar should add a new option to add custom task, and take you to a wizard or something so we don't have to remember how to create a custom task every time. |
|
Don't give them ideas. The status bar does not do justice for our needs because after installing a few extensions the status bar becomes a cluttered mess with tiny icons. I've been using IntelliJ's IDE instead of VS Code and the toolbar is a bliss (along with detachable tabs). And this is what we need in VS Code. I would even welcome a big customizable toolbar with tabs like in MS Office. But a classic toolbar would suffice. Programs like Open Office have options to switch between classic, tabbed or no toolbars. What is stopping us? |
|
This makes me miss Githib's Atom |
and others
Whole my life I used ide where there was a customizable toolbar. I starded to use vscode and stopped to use it after one day. It is impossible to remember all shorcuts. In any other popular ide you can put any menu item on toolbar and use it from time to time.
visual vtudio:
idea:
eclipse:
netbeans:
code blocks:
komodo ide:
atom:
notepad++:
gedit:
github:
WTF MS? VS code? VS users?
Don't tag it "out-of-scope" as you did before with similar requests. Even simple editors have toolbar.
It isn't advanced feature it's basic feature for most people.
Using ide without toolbar is not user friendly for most users. It is vim way.
People really need it like "exit from vim":
FAQ FOR PEOPLE WHO ARE AGAINST THE TOOLBAR:
It is not a problem "it is optional toolbar". If you don't want you can don't use it.
People have offered, go look at the many other bug reports made on the same issue. MS has said they would likely reject it. They don't even want to add hooks to make a plugin possible. So it's not a resource issue, it's an ideological one.
Temporary workaround by @GorvGoyl:
The text was updated successfully, but these errors were encountered: