Debug: major theming improvements 🎨 🎉#94838
Debug: major theming improvements 🎨 🎉#94838isidorn merged 4 commits intomicrosoft:masterfrom robertrossmann:feat/debug-theming-improvements
Conversation
|
@robertrossmann thanks a lot for this awesome PR, overall great work, I really like it! Feedback:
Also assigning to @misolori for designer review and @aeschli for review of color names. |
|
@isidorn Thank you for your feedback! I will address it now. 💪
I am not sure if I understand this correctly, but I did not really add any new colours, I merely took the existing hard-coded colours and made them themeable. The colour contributions are listed in the original description, including a screenshot of the thing they apply to. For completness' sake, here they are listed again in full.
To summarise which colours are now different in writing:
|
|
I just noticed that the variable names in the Variables sub-view have different colour in dark variants in this PR. This was unintentional - I just force-pushed a fix for that. I won't update the screens, though - it's too much work. 😇 |
|
Did another review and left comments in the code. It would be great if you could tackle them. Yes I meant color names, so @aeschli can verify those. And once we get his feedback and @misolori feedback I will try this out a bit more and if it looks good we can merge in next week. I am also not a fan of Thanks! |
|
Also something to keep in mind: if we ever want to make the debug colors more inlined with the language color. For example debug while deubgging javascript might want to color strings the same way as javascript colors them. This goes a bit against that. But I think that is fine. Though @weinand might be better to decide since he is looking into potential debug / language integration. |
|
@isidorn Thanks for review - all concerns have been addressed. Regarding using language token colours for the debug views - that would be the ideal scenario, of course! Until then, however, I would love to have at least something to appease my inner artistic gods. They scream loud and shudder violently whenever I start a debugging session. 😂 |
|
@robertrossmann Great work, you have my provisional approve. In the future if we get nice coloring from languages then we can deprecate some of these colors. |
|
Color names look good to me! |
|
@robertrossmann I found ony copy paste error in the description. Once you tackle that we can merge this in. |
|
@isidorn Thanks, I fixed the typo, squashed the review commits and rebased on current master. Excited to have this merged! 🎉 🍻 |
|
Great work, merging in. Thank you very much! ☀️ |
|
Thanks @isidorn, I would have sworn that I tested the hovers as well! 😱 👍 ❤️ |
|
@robertohuertasm thanks ton for pushing this 👍 |
Very bleeding-edge. Not even on Insiders yet as of this commit. 🤷♂️ See microsoft/vscode#94838
|
@robertrossmann not sure if you are interested but in case you would like these colors being used in our default themes we are open for a PR that tackles that. Of course if @misolori agrees. |
|
@isidorn I think I can contribute to some themes but I am not sure if I can work on all the themes that ship with VS Code by default. 😢 Perhaps the more colourful ones would benefit the most from custom theming (Kimbie, Red, Solarized) ? The default colours work relatively well for the other themes. @misolori Let us know what you think, we can perhaps split the work or do it incrementally as time permits. 💪 |
|
Yeah, sounds good. I definetly agree that only the more colorful one should use the new colors. |
# [4.7.0](4.6.2...4.7.0) (2020-04-15) ### Bug Fixes * add meta.brackets to punctuation scope ([499c8b9](499c8b9)) * use correct colour for C hex constants, straighten some brackets ([3992712](3992712)) ### Features * add theming for new debug-related colour contributions 🎨 ([d3bc557](d3bc557)), closes [microsoft/vscode#94838](microsoft/vscode#94838)
|
@robertrossmann I agree that only the other non-default themes should start using the new color tokens. Feel free to ping me in your PR if you want any feedback on your proposals. Thanks again for doing this work 💪! |








This PR introduces several new colour contribution points for many parts of the Debug UI. The vast majority revolves around the stack trace viewlet and the various colours used for showing variables across the debug panel, and the debug REPL.
Here is the list of new colour contributions. Please be aware that the screenshots below contain colours I overrode while working on this, they dot not represent the default colours in this PR.⚠️ I kept the original color values as defaults for all the new colour contributions in vast majority of situations. There might be a slight deviation here and there to fix contrast but the overal look and feel should be relatively the same.
Looking forward to hear your feedback! 👀
Stack trace viewlet
debugView.exceptionLabelForegrounddebugView.exceptionLabelBackgrounddebugView.stateLabelForegrounddebugView.stateLabelBackgrounddebugView.valueChangedHighlightDebug REPL
<- Removed as per reviewdebugConsole.warningForeground<- Removed as per reviewdebugConsole.annotationForegroundVariables / tokens & values
debugTokenExpression.namedebugTokenExpression.valuedebugTokenExpression.stringdebugTokenExpression.booleandebugTokenExpression.numberdebugTokenExpression.errorOther changes
The line/column position info in the stack trace viewlet now uses the same colours as a regular "badge" (
badge.foreground&badge.background)The filename in the stack trace viewlet now uses the same colour as for list's deemphasized content (
list.deemphasizedForeground)The debug REPL's input box border now uses the input border colour (
input.border) if defined, otherwise it defaults back to the original colour used before this PR.Overall look and feel