-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Dark vs Light, Printing? #464
Comments
|
(1a) You have a light Gruvbox for KiCad??? (1b) Yes I found the contrib list. My observation is that KiCad isn't listed as one of the adaptations of Gruvbox. (2) I think that is okay. In printing schematics there is an option to replace the background colors. |
However, I just tried create a light theme, you can check my work in this repo. I believe light and dark are quite similar, with most colors being the same or very close. The main difference lies in the bg and fg. Both options cater to those who prefer light text on dark bg or dark text on light bg, allowing everyone to experience the gruvbox style. |
This is a high-level question, two parts.
(1) Alexander Brevig has adapted Gruvbox for use in KiCad, a popular open-source PCB CAD design tool. I don't see his adaptation on your list, would it be appropriate to add it?
(2) I find this color scheme perfect for PCB and schematic layout, although I realize it is far afield from the intended use in vim (I use it in vim, too). But here's a problem I face -- printing a hard copy. Yeah, we still need to do that from time to time these days. If you print it normally, you'd use up a ton of black ink/toner. If you tell the program to use a white background (and not change any other colors), the contrasts are all wrong. Consider that yellow features jump out at you against a dark background, but can be barely visible against a white background.
Can gruvbox light be considered the "opposite" of dark, in the sense that it can be printed on white paper with good results? Or is it its own unique collection of colors, unrelated to dark?
The text was updated successfully, but these errors were encountered: