1426cd3b3a
As many open source projects have started doing it, we're removing the current year from the copyright notice, so that we don't need to bump it every year. It seems like only the first year of publication is technically relevant for copyright notices, and even that seems to be something that many companies stopped listing altogether (in a version controlled codebase, the commits are a much better source of date of publication than a hardcoded copyright statement). We also now list Godot Engine contributors first as we're collectively the current maintainers of the project, and we clarify that the "exclusive" copyright of the co-founders covers the timespan before opensourcing (their further contributions are included as part of Godot Engine contributors). Also fixed "cf." Frenchism - it's meant as "refer to / see". Backported from #70885. |
||
---|---|---|
.. | ||
doc_classes | ||
extensions | ||
structures | ||
config.py | ||
editor_scene_exporter_gltf_plugin.cpp | ||
editor_scene_exporter_gltf_plugin.h | ||
editor_scene_importer_gltf.cpp | ||
editor_scene_importer_gltf.h | ||
gltf_defines.h | ||
gltf_document.cpp | ||
gltf_document.h | ||
gltf_state.cpp | ||
gltf_state.h | ||
gltf_template_convert.h | ||
packed_scene_gltf.cpp | ||
packed_scene_gltf.h | ||
README.md | ||
register_types.cpp | ||
register_types.h | ||
SCsub |
Godot GLTF import and export module
In a nutshell, the GLTF module works like this:
- The
structures/
folder contains GLTF structures, the small pieces that make up a GLTF file, represented as C++ classes. - The
extensions/
folder contains GLTF extensions, which are optional features that build on top of the base GLTF spec. GLTFState
holds collections of structures and extensions.GLTFDocument
operates on GLTFState and its elements.