GDExtension docs

Author: paddy-exe

tutorials/scripting/gdnative/files/cpp_example/SConstruct renamed to tutorials/scripting/gdextension/files/cpp_example/SConstruct

@@ -1,6 +1,6 @@
 .. _doc_gdnative_c_example:
 
-GDNative C example
+GDExtension C example
 ==================
 
 Introduction

tutorials/scripting/gdnative/gdnative_c_example.rst renamed to tutorials/scripting/gdextension/gdextension_c_example.rst

@@ -1,6 +1,6 @@
-.. _doc_gdnative_cpp_example:
+.. _doc_gdextension_cpp_example:
 
-GDNative C++ example
+GDExtension C++ example
 ====================
 
 Introduction

tutorials/scripting/gdnative/gdnative_cpp_example.rst renamed to tutorials/scripting/gdextension/gdextension_cpp_example.rst

@@ -0,0 +1,10 @@
+GDExtension
+========
+
+.. toctree::
+   :maxdepth: 1
+   :name: toc-tutorials-gdextension
+
+   what_is_gdextension
+   gdextension_c_example
+   gdextension_cpp_example

tutorials/scripting/gdnative/img/add_main_script.gif renamed to tutorials/scripting/gdextension/img/add_main_script.gif

@@ -1,77 +1,74 @@
-.. _doc_what_is_gdnative:
+.. _doc_what_is_gdextension:
 
-What is GDNative?
+What is GDExtension?
 =================
 
 Introduction
 ------------
 
-**GDNative** is a Godot-specific technology that lets the engine interact with
+**GDExtension** is a Godot-specific technology that lets the engine interact with
 native `shared libraries <https://en.wikipedia.org/wiki/Library_(computing)#Shared_libraries>`__
 at run-time. You can use it to run native code without compiling it with the engine.
 
-.. note:: GDNative is *not* a scripting language and has no relation to
+.. note:: GDExtension is *not* a scripting language and has no relation to
           :ref:`GDScript <doc_gdscript>`.
 
-Differences between GDNative and C++ modules
+Differences between GDExtension and C++ modules
 --------------------------------------------
 
-You can use both GDNative and :ref:`C++ modules <doc_custom_modules_in_c++>` to
+You can use both GDExtension and :ref:`C++ modules <doc_custom_modules_in_c++>` to
 run C or C++ code in a Godot project.
 
 They also both allow you to integrate third-party libraries into Godot. The one
 you should choose depends on your needs.
 
-Advantages of GDNative
+Advantages of GDExtension
 ^^^^^^^^^^^^^^^^^^^^^^
 
-Unlike modules, GDNative doesn't require compiling the engine's source code,
+Unlike modules, GDExtension doesn't require compiling the engine's source code,
 making it easier to distribute your work. It gives you access to most of the API
 available to GDScript C#, allowing you to code game logic with full control
 regarding performance. It's ideal if you need high-performance code you'd like
 to distribute as an add-on in the :ref:`asset library <doc_what_is_assetlib>`.
 
 Also:
 
-- GDNative is not limited to C and C++. Thanks to :ref:`third-party bindings
+- GDExtension is not limited to C and C++. Thanks to :ref:`third-party bindings
   <doc_what_is_gdnative_third_party_bindings>`, you can use it with many other
   languages.
-- You can use the same compiled GDNative library in the editor and exported
+- You can use the same compiled GDExtension library in the editor and exported
   project. With C++ modules, you have to recompile all the export templates you
   plan to use if you require its functionality at run-time.
-- GDNative only requires you to compile your library, not the whole engine.
+- GDExtension only requires you to compile your library, not the whole engine.
   That's unlike C++ modules, which are statically compiled into the engine.
   Every time you change a module, you need to recompile the engine. Even with
-  incremental builds, this process is slower than using GDNative.
+  incremental builds, this process is slower than using GDExtension.
 
 Advantages of C++ modules
 ^^^^^^^^^^^^^^^^^^^^^^^^^
 
 We recommend :ref:`C++ modules <doc_custom_modules_in_c++>` in cases where
-GDNative isn't enough:
+GDExtension isn't enough:
 
-- C++ modules provide deeper integration into the engine. GDNative's access is
-  limited to what the scripting API exposes.
+- C++ modules provide deeper integration into the engine. GDExtension's access is not as deep as
+  static modules
 - You can use C++ modules to provide additional features in a project without
   carrying native library files around. This extends to exported projects.
-- C++ modules are supported on all platforms. In contrast, GDNative has only
-  limited support on HTML5 (cannot be used together with multi-threading), and
-  is not supported on Universal Windows Platform (UWP).
-- C++ modules can be faster than GDNative, especially when the code requires a
-  lot of communication through the scripting API.
+(- C++ modules can be faster than GDNative, especially when the code requires a
+  lot of communication through the scripting API.) -> TODO: check if this still holds up
 
 Supported languages
 -------------------
 
 The Godot developers officially support the following language bindings for
-GDNative:
+GDExtension:
 
 - C++ :ref:`(tutorial) <doc_gdnative_cpp_example>`
 - C :ref:`(tutorial) <doc_gdnative_c_example>`
 
 .. note::
 
-    There are no plans to support additional languages with GDNative officially.
+    There are no plans to support additional languages with GDExtension officially.
     That said, the community offers several bindings for other languages (see
     below).
 
@@ -98,9 +95,9 @@ The bindings below are developed and maintained by the community:
 Version compatibility
 ---------------------
 
-:ref:`Unlike Godot itself <doc_release_policy>`, GDNative has stricter version
-compatibility requirements as it relies on low-level *ptrcalls* to function.
+(:ref:`Unlike Godot itself <doc_release_policy>`, GDExtension has stricter version
+compatibility requirements as it relies on low-level *ptrcalls* to function.) -> TODO: check up on this
 
-GDNative add-ons compiled for a given Godot version are only guaranteed to work
-with the same minor release series. For example, a GDNative add-on compiled for
-Godot 3.4 will only work with Godot 3.4, 3.4.1, 3.4.2… but not Godot 3.3 or 3.5.
+GDExtension add-ons compiled for a given Godot version are only guaranteed to work
+with the same minor release series. For example, a GDExtension add-on compiled for
+Godot 4.0 will only work with Godot 4.0, 4.0.1, 4.0.2… but not Godot 3.5 or 3.6.