-
Notifications
You must be signed in to change notification settings - Fork 32.5k
Rename "Debug" to "Run" #90445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@luabud are you maybe planning to do more of the python user studies in the near future? I am asking since we renamed the Debug viewlet to Run and I am wondering if this will have a positive effect. |
@isidorn Definitely! We have one coming up on Feb 20 around the same subject 👍. We'll use VS Code Insiders then 😊. |
I do have an alternate icon (based on @weinand's suggestion) we can use. We can create a custom build for this or enable on Insiders to test this if we want to: |
@misolori I actually like that icon. Let's just go crazy and push it to insiders. You only live once. I will handle the haters on GitHub. @luabud great, let us know how it goes. Thanks a lot! |
I actually like the current strokes and size so it is larger than the number notification that can appear on the right corner (number of sessions). But we can experiment with different strokes. |
We want to convey the message that with this view a user can "Run" the program (corresponding to the newly renamed menu "Run"). |
I can definitely tweak the size and stroke of the bug. I’ll add it to Insiders today. |
Great, thanks! |
I've tweaked the icon a bit, it was hard to make it smaller as it became tiny in relation to the rest but this was the best I could get to: This is now in via e4c77cd and should be in tomorrow's Insiders |
Thanks @misolori I just got the new icon. It works for me. |
yes, increase the size of the arrow (but not the size of the bug). |
I really like the new icon. Speaks two things at once! |
So far feedback has been very positive. |
We did a run study last week with 8 participants for Settings Sync and one of the scenarios was to install the Python extension and run a python file. Most went to the terminal to run it, when asked to try an alternate way in the editor they used the "Run" menu. Two noticed the green "play" button and ran it that way, and two others went to the debug viewlet (when asked why they both said they've used the debugger before). |
@luabud let us know if you were able to run any other quick pulse studies that tested the new updates. |
We did! It was with 4 students, 2 went for the "Run" menu at first, and 2 went for the green play button on the top right. When we asked to try an alternate way, two right clicked on the editor, and the other two went for the "Run" menu. On the 3rd time, 3 of them went for the debug viewlet, and one for the run button on the top right - and for this one, the debug viewlet was the 4th alternative. When we asked about their preference, they all said they preferred the green run button on the top right as it's a one-click solution, and 2 of them mentioned the green colour as being what called their attention. |
@luabud thanks for letting us know and for running this study! So there seems to be a postiive effect. |
Yes, definitely! |
Motivation: new users do not know how to run their apps and are not aware that debugging can be used to achieve this when no breakpoints are set or with Debug: start without debugging action.
Current state
The text was updated successfully, but these errors were encountered: