25b2f1780a
This applies our existing style guide, and adds a new rule to that style
guide for modular components such as platform ports and modules:
Includes from the platform port or module ("local" includes) should be listed
first in their own block using relative paths, before Godot's "core" includes
which use "absolute" (project folder relative) paths, and finally thirdparty
includes.
Includes in `#ifdef`s come after their relevant section, i.e. the overall
structure is:
- Local includes
* Conditional local includes
- Core includes
* Conditional core includes
- Thirdparty includes
* Conditional thirdparty includes
|
||
|---|---|---|
| .. | ||
| doc_classes | ||
| editor | ||
| extensions | ||
| structures | ||
| config.py | ||
| gltf_defines.h | ||
| gltf_document.cpp | ||
| gltf_document.h | ||
| gltf_state.cpp | ||
| gltf_state.h | ||
| gltf_template_convert.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. GLTFStateholds collections of structures and extensions.GLTFDocumentoperates on GLTFState and its elements.- The
editor/folder uses GLTFDocument to import and export 3D models.