You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ To start contributing, fork this repository, then use the following debug script
23
23
24
24
- Run **New Window with VSCode Theme** to open a new window that responds to generated theme file changes in real-time.
25
25
26
-
Use a [colour mixer](https://colordesigner.io/color-mixer) to experiment with colours and shades.
26
+
Use a [colour mixer](https://colordesigner.io/color-mixer) to experiment with colours and shades, and [ANSI-Color-Test](https://github.com/nesterenkovy/ANSI-Color-Test) to preview terminal colours.
27
27
28
28
Pull requests are welcome. Please provide a description and screenshots of your changes.
Copy file name to clipboardExpand all lines: docs/colours.md
+97-9Lines changed: 97 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -178,10 +178,12 @@ The active icon border should be disabled, as it is distracting. Instead, a back
178
178
179
179
Icon badges in Visual Studio Code are meant to represent notifications, however they are used for a large variey of purposes, so many that their presence becomes somewhat of an annoyance. In my theme their background should be toned down, though still be visible. Their foreground can be the same as the active icon colour for simplicity.
180
180
181
-
Before creating this theme, I used #404040, which is surprisingly too bright of a colour. I have instead taken the inactive icon background and mixed it with the activity bar background, using a 2:5 mix. Any darker and it becomes hard to tell if there is even a badge there. Any brighter and it becomes distracting.
181
+
Before creating this theme, I used #404040, which is surprisingly too bright of a colour. I have instead taken the inactive icon background and mixed it with the activity bar background, using a 2:5 mix. Any darker and it becomes hard to tell if there is even a badge there. Any brighter and it becomes distracting. (For now, all other badges use the same colours.)
182
182
183
183
> -`activityBarBadge.background`
184
184
> -`activityBarBadge.foreground`
185
+
> -`badge.background`
186
+
> -`badge.foreground`
185
187
186
188
### Text
187
189
@@ -206,6 +208,25 @@ Ignored files and folders ought to have a much darker text colour than normal te
206
208
207
209
> -`gitDecoration.ignoredResourceForeground`
208
210
211
+
The other Git decoration colours are borrowed from semantic colours in this theme.
212
+
213
+
-*Added*/*Untracked*: The function colour
214
+
-*Conflicting*: The warning colour
215
+
-*Deleted*: The class colour
216
+
-*Modified*: The constant variable colour (as the normal variable colour is too bright compared to the sidebar text colour)
217
+
-*Renamed*: The variable colour (the better-looking out of the two colours adjacent to the constant variable colour)
As in Markdown files, the text in code blocks is given the colour of variables. This appears most often in Visual Studio Code's settings when describing a setting.
@@ -320,6 +341,22 @@ Before creating this theme, I used `#1da1f2fe`. The alpha of #fe was likely a re
320
341
321
342
> -`extensionIcon.verifiedForeground`
322
343
344
+
### Testing
345
+
346
+
The icons that appear in the Testing view share their colours with other semantic colours in this theme.
347
+
348
+
-*Unset*/*Queued*: The comment colour
349
+
-*Passed*: Same as `debugIcon.startForeground` (`debugIcon.continueForeground` is too bright)
350
+
-*Skipped*: The warning colour
351
+
-*Errored*/*Failed*: The error colour
352
+
353
+
> -`testing.iconUnset`
354
+
> -`testing.iconQueued`
355
+
> -`testing.iconPassed`
356
+
> -`testing.iconSkipped`
357
+
> -`testing.iconErrored`
358
+
> -`testing.iconFailed`
359
+
323
360
## Editor Area
324
361
325
362
### Background
@@ -402,6 +439,18 @@ Before creating this theme, I used an alpha of `#20`, but this is a bit too brig
402
439
> -`selection.background`
403
440
> -`editor.inactiveSelectionBackground`
404
441
442
+
### Difference Indicators
443
+
444
+
Text difference indicators should not change from their well-known colours, red and green, but they must be set to the correct lightnesses and transparencies so that they do not obscure any text, especially comments.
445
+
446
+
<!-- TODO: Revisit these colours when making light theme -->
447
+
From initial testing, a dark red and bright green were chosen, specifically `#0d351a` (the darkest yet most legible red) and `#0c2f18` (a 10:1 mix of the editor area colour and pure green). However, these opaque colours would not be compatible with theme variants. To rectify this, green was changed to `#00ff0018` (a near identical match) and red to `#ff00002b` (roughly equal to green in terms of lightness). The highlight colours are identical.
448
+
449
+
> -`diffEditor.removedLineBackground`
450
+
> -`diffEditor.insertedLineBackground`
451
+
> -`diffEditor.removedTextBackground`
452
+
> -`diffEditor.insertedTextBackground`
453
+
405
454
### Scroll Bar
406
455
407
456
Due to the very faint colours in use by various selection components in this theme, the scrollbar needs to be able to show these while still remaining visible. The alphas for the below three states (seen in order) were chosen carefully to maintain a visual distinction between each state while remaining dark and still showing what is behind them.
@@ -469,8 +518,8 @@ The debug toolbar's icons are given colours similar to the sematic colours in th
469
518
-*Pause*: The variable colour, for it exposes variables and is more visible than the type colour
470
519
-*Continue*: The value colour, for it is green
471
520
-*Step Over*: The function colour, for it implies running a function
472
-
-*Step Into*/*Step Back*: A 1:1 mix of the function and control flow colours, creating a linear gradient
473
-
-*Step Out*: The control flow colour, for it implies exiting a flow
521
+
-*Step Into*/*Step Back*: A 1:1 mix of the function and keyword colours, creating a linear gradient
522
+
-*Step Out*: The keyword colour, for it implies exiting a flow
474
523
-*Restart*: The type colour, for it is unused by the rest of the debug icons and creates a gradient between *Pause* and *Stop*
475
524
-*Stop*/*Disconnect*: The class colour, for it is red
476
525
@@ -505,21 +554,22 @@ Because the debug view in the sidebar represents actual programmatic concepts, t
505
554
> -`debugTokenExpression.type`
506
555
> -`debugTokenExpression.error`
507
556
508
-
### Outline Symbols
557
+
### Outline Symbol Icons
509
558
510
559
As with the debug view, the icons in the Outline also make use of the semantic colours in this theme.
511
560
512
-
-*Boolean*/*Null*/*Number*: The value colour
561
+
-*Boolean*/*Color*/*Null*/*Number*/*Unit*: The value colour
513
562
-*Class*/*Enum*/*Interface*/*Struct*: The class colour
514
563
-*Constant*/*Enum Member*: The constant variable colour (for variety)
515
-
-*Constructor*/*Function*/*Method*: The function colour
564
+
-*Constructor*/*Function*/*Method*/*Snippet*: The function colour
516
565
-*Event*/*Field*/*Key*/*Property*/*Variable*: The variable colour
517
-
-*Array*/*Module*/*Namespace*/*Object*/*Operator*/*Package*: The control flow colour
518
-
-*File*/*String*: The string colour
566
+
-*Array*/*Keyword*/*Module*/*Namespace*/*Object*/*Operator*/*Package*/*Reference*: The keyword colour
567
+
-*File*/*Folder*/*String*/*Text*: The string colour
519
568
-*Type Parameter*: The type colour
520
569
521
570
> -`symbolIcon.arrayForeground`
522
571
> -`symbolIcon.booleanForeground`
572
+
> -`symbolIcon.colorForeground`
523
573
> -`symbolIcon.constantForeground`
524
574
> -`symbolIcon.classForeground`
525
575
> -`symbolIcon.constructorForeground`
@@ -528,9 +578,11 @@ As with the debug view, the icons in the Outline also make use of the semantic c
528
578
> -`symbolIcon.eventForeground`
529
579
> -`symbolIcon.fieldForeground`
530
580
> -`symbolIcon.fileForeground`
581
+
> -`symbolIcon.folderForeground`
531
582
> -`symbolIcon.functionForeground`
532
583
> -`symbolIcon.interfaceForeground`
533
584
> -`symbolIcon.keyForeground`
585
+
> -`symbolIcon.keywordForeground`
534
586
> -`symbolIcon.objectForeground`
535
587
> -`symbolIcon.operatorForeground`
536
588
> -`symbolIcon.methodForeground`
@@ -540,11 +592,44 @@ As with the debug view, the icons in the Outline also make use of the semantic c
\*Shifted to saturation 61 value 100 (#6382ff)<br/>
626
+
\*\*Shifted to hue 318 saturation 51 value 100 (#ff7cd7)<br/>
627
+
\*\*\*Shifted to hue 200 value 90 (#b0d3e5)<br/>
628
+
^Shifted to saturation 100 + black alpha 50<br/>
629
+
^^Shifted to saturation 100 value 58 (#009304)<br/>
630
+
^^^Shifted to value 67 (#aaaa00)<br/>
631
+
^^^^Shifted to saturation 100 value 86 (#002cdd)
632
+
548
633
## Editor Text
549
634
550
635
### Text Colour
@@ -569,7 +654,7 @@ Whitespace characters must blend in thoroughly with the editor background while
569
654
570
655
Visual Studio Code has support for up to 6 different bracket colours, which appear in order when nesting occurs. The first colour is the outermost bracket, the colours looping if excessive levels of nesting exist.
571
656
572
-
As this theme has defined several semantic token colours, I am using those to define the bracket colours, starting from the control flow colour and sweeping through in the function direction to make a rainbow.
657
+
As this theme has defined several semantic token colours, I am using those to define the bracket colours, starting from the keyword colour and sweeping through in the function direction to make a rainbow.
573
658
574
659
> -`editorBracketHighlight.foreground1`
575
660
> -`editorBracketHighlight.foreground2`
@@ -583,17 +668,20 @@ As this theme has defined several semantic token colours, I am using those to de
583
668
Errors must be red, though the class semantic colour is not red enough. Using the same process, a 5:2 mix of `#ff0000` and `#ffffff` produces a more attention-grabbing red that is still legible on both the editor background and the current file selection.
584
669
585
670
> -`list.errorForeground`
671
+
> -`problemsErrorIcon.foreground`
586
672
> -`editorError.foreground`
587
673
> -`errorLens.errorForeground`
588
674
589
675
Similarly, warnings are somewhat orange, so the same approach is taken but for the type semantic colour, using a 6:1 mix of its components.
590
676
591
677
> -`list.warningForeground`
678
+
> -`problemsWarningIcon.foreground`
592
679
> -`editorWarning.foreground`
593
680
> -`errorLens.warningForeground`
594
681
595
682
As for the info colour, info messages tend to be very annoying, so rather than giving them their default hue of blue, they use a colour even darker than comments, a 5:2 mix of said colour and the editor background colour.
0 commit comments