stan220/godot-docs
1
0
Fork 0
mirror of https://github.com/stan220/godot-docs.git synced 2026-09-08 21:29:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #7299 from Ubiguchi/patch-1

Browse Source
This commit is contained in:
Max Hilbrunner
2023-05-15 01:22:09 +02:00
committed by GitHub
parent b42b87edd9 96d83a01cf
commit e13dc5d09a
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tutorials/best_practices/scenes_versus_scripts.rst
+2 -2
View File
@@ -11,8 +11,8 @@ declarative code.
Each system's capabilities are different as a result.
Scenes can define how an extended class initializes, but not what its
behavior actually is. Scenes are often used in conjunction with a script so
that the scene acts as an extension of the scripts declarative code.
behavior actually is. Scenes are often used in conjunction with a script,
the scene declaring a composition of nodes, and the script adding behaviour with imperative code.
Anonymous types
---------------
tutorials/best_practices/what_are_godot_classes.rst
+2 -2
View File
@@ -54,8 +54,8 @@ The behavior of scenes has many similarities to classes, so it can make sense to
a class. Scenes are reusable, instantiable, and inheritable groups of nodes. Creating a scene is
similar to having a script that creates nodes and adds them as children using ``add_child()``.
We often pair a scene with a scripted root node that makes use of the scene's nodes. As such, the
scene is often an extension of the script's declarative code.
We often pair a scene with a scripted root node that makes use of the scene's nodes. As such,
the script extends the scene by adding behavior through imperative code.
The content of a scene helps to define: