Go to file
Yuri Sizov 635b8a1474 Split theme generation logic into several subroutines
This change introduces a new theme configuration struct to be
passed to the aforementioned routines to better control reuse
of styles and definitions in the generator.

Everything not passed and not explicitly shared is scoped so it
is not automatically accessible throughout the routine. This
should ensure that the decision to share styles is a conscious one.

In the future we will try to reduce the number of unique definitions
and share most of it. This PR is a stepping stone on this path.

This also puts the effort into separating redefinitions of
default theme items vs custom types introduced only by the editor.
In a few cases where editor-specific definitions need to reference
default definitions we simply fetch them from the theme. It's not
ideal and hides the dependency a bit, but hopefully these cases
will be abstracted properly in due time.
2024-01-16 11:57:45 +01:00
.github Reorganize code related to editor theming 2024-01-16 11:57:45 +01:00
core Merge pull request #87169 from 0x0ACB/debugger_deadlock 2024-01-16 10:36:25 +01:00
doc Merge pull request #87223 from Mickeon/documentation-uncommon-words 2024-01-16 10:39:13 +01:00
drivers Merge pull request #87206 from bruvzg/dx12_old_msvc 2024-01-16 10:37:12 +01:00
editor Split theme generation logic into several subroutines 2024-01-16 11:57:45 +01:00
main
misc
modules Reorganize code related to editor theming 2024-01-16 11:57:45 +01:00
platform Reorganize code related to editor theming 2024-01-16 11:57:45 +01:00
scene Reorganize code related to editor theming 2024-01-16 11:57:45 +01:00
servers Merge pull request #87207 from jsjtxietian/fix-normal_roughness_compatibility 2024-01-16 10:37:37 +01:00
tests Reorganize code related to editor theming 2024-01-16 11:57:45 +01:00
thirdparty Merge pull request #87105 from capnm/240112_horvg_from_v0.12.0_to_0.12.1 2024-01-15 13:29:26 +01:00
.clang-format
.clang-tidy
.editorconfig
.git-blame-ignore-revs
.gitattributes
.gitignore
.lgtm.yml
.mailmap
AUTHORS.md
CHANGELOG.md
CONTRIBUTING.md
COPYRIGHT.txt
DONORS.md
gles3_builders.py
glsl_builders.py
icon_outlined.png
icon_outlined.svg
icon.png
icon.svg
LICENSE.txt
LOGO_LICENSE.txt
logo_outlined.png
logo_outlined.svg
logo.png
logo.svg
methods.py
platform_methods.py
README.md
SConstruct
scu_builders.py
version.py

Godot Engine

Godot Engine logo

2D and 3D cross-platform game engine

Godot Engine is a feature-packed, cross-platform game engine to create 2D and 3D games from a unified interface. It provides a comprehensive set of common tools, so that users can focus on making games without having to reinvent the wheel. Games can be exported with one click to a number of platforms, including the major desktop platforms (Linux, macOS, Windows), mobile platforms (Android, iOS), as well as Web-based platforms and consoles.

Free, open source and community-driven

Godot is completely free and open source under the very permissive MIT license. No strings attached, no royalties, nothing. The users' games are theirs, down to the last line of engine code. Godot's development is fully independent and community-driven, empowering users to help shape their engine to match their expectations. It is supported by the Godot Foundation not-for-profit.

Before being open sourced in February 2014, Godot had been developed by Juan Linietsky and Ariel Manzur (both still maintaining the project) for several years as an in-house engine, used to publish several work-for-hire titles.

Screenshot of a 3D scene in the Godot Engine editor

Getting the engine

Binary downloads

Official binaries for the Godot editor and the export templates can be found on the Godot website.

Compiling from source

See the official docs for compilation instructions for every supported platform.

Community and contributing

Godot is not only an engine but an ever-growing community of users and engine developers. The main community channels are listed on the homepage.

The best way to get in touch with the core engine developers is to join the Godot Contributors Chat.

To get started contributing to the project, see the contributing guide. This document also includes guidelines for reporting bugs.

Documentation and demos

The official documentation is hosted on Read the Docs. It is maintained by the Godot community in its own GitHub repository.

The class reference is also accessible from the Godot editor.

We also maintain official demos in their own GitHub repository as well as a list of awesome Godot community resources.

There are also a number of other learning resources provided by the community, such as text and video tutorials, demos, etc. Consult the community channels for more information.

Code Triagers Badge Translate on Weblate TODOs