-
-
Notifications
You must be signed in to change notification settings - Fork 23.7k
Add a new editor theme #111118
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
Add a new editor theme #111118
Conversation
c78ccd5 to
6b7566d
Compare
This comment was marked as resolved.
This comment was marked as resolved.
I know this is subjective, but: OptionButton in top left corner ("ArcadeMachine") has too big margins compared to all other Controls. Same is valid for "Add Metadata" button. |
was this decided somewhere? there's no linked proposal (nor could i find one that this issue specifically addresses except maybe godotengine/godot-proposals#8264) how does this interact with light theme? is there a light variant of this or is the light theme going to revert to the default spacings? |
The current color presets are all there, including the light theme. |
|
Font is changed to Inter. What about visual consistency across languages compared to Noto Sans? |
Metrics seems similar, so should not be an issue. But we probably should allow overriding language specific fonts (not as part of this PR, I'll look at it a bit later). |
This comment was marked as resolved.
This comment was marked as resolved.
|
@KoBeWi That actually seems to be a regression from another PR. Notice how the theme names don't have spaces anymore in your video, while the code that checks them does. |
|
Related: godotengine/godot-proposals#9012 |
|
These are difficult to discuss as it can quickly get opinionated and subjective, but I feel like the value of the grey color is a bit too dark. |
As someone who's been using this theme for years, I consider the lower visual noise on the scene dock, debugger and inspector panels an upside. It's just as jarring to see the current design after being used to the minimal theme as it is the other way around. I agree that the other two could definitely use some love. Although the tileset editor looks kinda random in both themes. |
If it isn't much to suggest, would be good to have |
Co-authored-by: passivestar <[email protected]>
f96841b to
e06f015
Compare
akien-mga
left a comment
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.
Great work @YeldhamDev and @passivestar, and everyone reviewing so far!
This seems in a pretty good state to merge now and get more testing. The PR is already quite big and handling all remaining feedback in a big PR is cumbersome.
So we're aware that some feedback is still unaddressed, but let's keep track of it in dedicated issues and fix it in follow-up PRs, so we can fine tune the details and ensure most users are satisfied with the new theme by the time 4.6-stable releases.
Merging this now means that the first version will be available in the upcoming 4.6-dev3 snapshot, but again further work will be done during the dev (and maybe beta) phase to polish it up.
|
Thanks! Excellent job to everyone involved for bringing this together! |
|
Hey, why is this becoming the new theme? Why are we removing the darker inner BG of these UI elements so they're one giant flat color with no visual breakup? Look at the input map dialogue in this comment, the list of all the inputs and the dropdowns have all the elements the same color in the new theme! They were visually distinct before! |
|
The new theme will be iterated based on feedback. |
|
Making a theme default is tacit endorsement of the design of that theme. I don't wish for future design choices to be based off of this theme. |
|
this really, really should not be the default theme yet. without going into nitpicking everything, read and consistency are fairly significantly worse across the board. |
|
Without getting caught up in my own personal nitpicks with this chosen theme (of which I have many), I would hope that function and usability remains the primary factor by which any default theme is selected. Functionally, there appears to be a loss in effective screen real estate for many elements, as they now take up more space than before. And as pointed out a moment ago, the new Input Map is simply a downgrade. I can't see a good argument for this as it currently exists. As a positive, I like the new scene and file browser list density, as they both display more items than before in the same space. (Would still prefer a return of a darker background element to help distinguish the item list, though.) Subjectively, I find this new theme quite difficult to look at. I find this shade of color to be very disagreeable, and I can't recall a time in any software I've ever used where a dark mode theme was similar to this tone. Again, this is a subjective complaint, but I also would argue that a theme based around a highlighter yellow base would not be a great default choice either. Personally, I think a color selection closer to the existing default theme would help a lot. |
|
Now that this has been merged, you should create new issues instead of continue commenting in this PR. Otherwise, some of the feedback might end up falling through the cracks. |
|
Some of this feedback was already in the thread for a month, like the concerns about the solid-color backgrounds. Why do I have to make a new issue when it was ignored? Additionally, where was it decided that this would be the new theme? That comment still hasn't been addressed. I don't think it's wise to barrel forward with a large UI change that most of the userbase won't be aware of until it's out! I only just became aware an hour after it was merged. |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Creating new issues for problems that still exists. will cost time that could have been spent better. Think this process could have been handled better. Like a proposal where a discussion of what needs to improve, why etc, to get the best result.
That comment feels a bit unnecessary. We all want to get best the result here. Hopefully that's where we end up when this is done :) |
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.
Why not call it "minimal" instead of "modern"? The word "modern" is a nebulous term akin to "updated".
|
Could we have a project tracker for issues/PRs related to this? I'm not sure how they're usually handled but would find it helpful for seeing progress and preventing overlap. So far, I've seen: |
|
Although it looks slick, but the blending of menus and tabs and lists is confusing, I hope in the next version we can differentiate, like in scene tab we can still have trees lines between parent child nodes, and different color gradient to separate each menu or submenus. |
|
Do note for anyone reading this, we are keeping track of all issues opened about the new theme. So, although it's being repeated constantly, it would be beneficial to the community as a whole to open unique, individual issues to provide specific feedback about the new theme and discuss potential solutions. Side note, this PR has the potential to uncover certain omissions with "custom themes" as a whole, which personally has me confident it's going to make the general UX more consistent going forward! |















Is with great pleasure that I present you, Godot's soon-to-be new default theme!
This is a 1:1 port of @passivestar's Minimal Theme, with himself also helping us behind the curtains in order to facilitate the porting work. The editor font used is now Inter, and the new theme also changes the editor's base color and accent. While the blue tint had become a staple of Godot’s look over the past years, it caused issues such as distorting the perceived white balance of the viewport. Switching to a neutral gray resolves this.
But for those who still liked the older look better, fret not, As the old theme and color preset is still available, for you to pick! They can be accessed by choosing "Classic" in the
interface/theme/styleandinterface/theme/presetsettings.While this PR is in a merge-able state, some small things still need to be worked on:
NestedTabContainers blend with each other.The disabled tab style is a placeholder, while waiting for passive to implement it.PopupMenus still look very squarish, as Makeper_pixel_transparencyalways enabled in the editor #106324 still needs to be resolved.Feedback is more than welcome, but please, keep it civil. Topics involving theming and design are very subjective, so the more objective information you can provide about your issues the easier it will be to address them in future PRs.