godotengine/godot-docs
1
0
Fork 0
mirror of https://github.com/godotengine/godot-docs.git synced 2026-01-05 22:09:56 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update description of scenes' use of declarative code

Browse Source 
Tighten language  mentioning scenes' use of declarative code and scripts use of imperative code.
This commit is contained in:
Mark J. Easton
2023-05-06 21:52:03 +01:00
committed by Mark Easton
parent c0d9c61e6d
commit 96d83a01cf
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
tutorials/best_practices/scenes_versus_scripts.rst
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
---------------

4
tutorials/best_practices/what_are_godot_classes.rst
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: