-
Notifications
You must be signed in to change notification settings - Fork 195
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
Update GitHub Dark + test GitHub Dimmed #98
Conversation
The plan is: 1. Rename "GitHub Dark" to "GitHub SpaceGray" 2. Use new dark colors for "GitHub Dark"
Not sure if this is a better name, but it relates to what VS Code calls "uiTheme".
Co-Authored-By: Boris Krstic <[email protected]>
For names, what about |
The activity bar in the |
Yeah,
Yes, right. I just updated the screenshots. Might still need some more tweaking. |
Something off the topic but I just wonder what is icon theme in the screenshot? @simurai Thanks. |
It's the City Lights Icon package. It has an option where you can make the icons monochrome. Harder to differentiate, but a bit calmer. 😄 |
Thanks! |
I had the idea of seeing same on browser and vscode, thanks for bringing consistency here, hope it would be merged soon 💯 |
this PR solves many consistency problems but I wanted to give feedback while I already started to use this one. I put an examle here for this file: https://github.com/keremciu/house-of-decks/blob/ws-implement/client/src/Components/Button.js I could try help if it's possible to make this reach and JavaScript implementation more consistent |
I wanted to ask if the theme is synced with the official github dark mode, and if not, is there any eta? |
Looking forward to this update. Is there anything we can help with? |
I tried to update just by looking for JavaScript react highlighting differences. keremciu@679cec8#diff-09ce39aad75bba2010ea6e7fb785187ec76b341be11d5f7f2cc6b83839a1b728 don't know if this is a sustainable way to make changes while I have no idea what GitHub uses for the interface :) I can confirm that my react code highlighting works consistent with this change, it can be improved of course. if someone can help to try it out, I can go deeper :) |
@tejasag, @nonameolsson, @Gameghostify It might will take a bit longer since we're still trying to improve the "dimmed" version. But you can already test it with:
Eventually I would delete it again since it won't get any updates. |
I just tried this one out and it looks so damn good! This theme is gonna take over 💯. Thank you so much for your hard work 🙏 |
Added it to this PR #100 including a couple screenshots to compare. I can spot changes to these "JSX tabs" like |
This build seems to work well except that additions are highlighted in red (and deletions in green) in the diff editor! |
src/theme.js
Outdated
"editorGutter.deletedBackground" : color.diff.deletion.border, | ||
|
||
"diffEditor.insertedTextBackground": color.diff.addition.bg, | ||
"diffEditor.removedTextBackground": color.diff.deletion.bg, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These colors are stored as rgba()
in the dark themes in @primer/primitives, but VSCode needs them to be in #RRGGBBAA
form here. My VSCode defaults them to a very bright and opaque red or green on the dark modes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Yes, seems VS Code only allows the #RRGGBBAA
format for transparency. When using rgba()
it defaults to red
:
Hmm.. seems that rgba()
has slightly better browser support, so we might still wanna keep using it for @primer/primitives
. For the VSCode theme we could try to convert it to #RRGGBBAA
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kherock thanks for reporting this! Was just about to report it myself :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, it's currently fixed by wrapping the @primer/primitives
color with a chroma(...).hex()
that supports #RRGGBBAA
:
But it could break anytime if @primer/primitives
uses rgba()
for any of the other colors. Would be better if we could convert all colors before generating the theme.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jeffgennari Yes.. thanks for spotting this. Should be fixed with 66bc8f0.
So we can use the `#RRGGBBAA` format that VS Code needs.
github.com now has an official dark mode. To keep this theme close to github.com, this PR does the following:
GitHub Dark
theme to a new repo -> github-vscode-theme-darkGitHub Dark
with the new colors. There is already a PR sync dark colors with new official GitHub dark theme #95 that we could try to merge into this one.GitHub Dimmed
theme.GitHub Dimmed
theme.Nice to have:
rgba()
colors fromprimer/primitives
to#rrggbbaa
. VS Code doesn't allowrgba()
and falls back tored
. Currently it uses this workaround but that isn't a great long-term solution.