123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243 |
- .. _doc_reference_filling_work:
- Reference filling work
- ======================
- Godot Engine provides an important number of classes that you can make
- use of to create your games. However, the :ref:`toc-class-ref` that
- lists all these classes with their methods is quite incomplete. We need
- your kind help to fill this reference. This page will explain you how.
- > Please note: we aim at filling completely this reference in English
- first. Please do not start translating it for the moment.
- :ref:`doc_list_of_classes_and_documenters`
- Editing with Github
- -------------------
- Fork Godot Engine
- ~~~~~~~~~~~~~~~~~
- First of all, you need to fork the Godot Engine on your own GitHub
- repository.
- You will then need to clone the master branch of Godot Engine in order
- to work on the most recent version of the engine, including all of its
- features.
- ::
- git clone https://github.com/your_name/godot.git
- Then, create a new git branch that will contain your changes.
- ::
- git checkout -b reference-edition
- The branch you just created is identical to current master branch of
- Godot Engine. It already contains a doc/ folder, with the currently
- written reference.
- Updating the documentation template
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- When classes are modified in the source code, the documentation template
- might become outdated. To make sure that you are editing an up-to-date
- version, you first need to compile Godot (you can follow the
- :ref:`doc_introduction_to_the_buildsystem` page), and then run the
- following command (assuming 64-bit Linux):
- ::
- ./bin/godot.x11.tools.64 -doctool doc/base/classes.xml
- The doc/base/classes.xml should then be up-to-date with current Godot
- Engine features. You can then check what changed (or not) using the
- ``git diff`` command. If there are changes to other classes than the one
- you are planning to document, please commit those changes first before
- starting to edit the template:
- ::
- git add doc/base/classes.xml
- git commit -m "Sync classes reference template with current code base"
- You are now ready to edit this file to add stuff.
- Push and request a pull of your changes
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Once your modifications are finished, push your changes on your GitHub
- repository:
- ::
- git add doc/base/classes.xml
- git commit -m "Explain your modifications."
- git push
- When it's done, you can ask for a Pull Request on the GitHub UI of your
- Godot fork.
- Edit doc/base/classes.xml file
- ------------------------------
- First of all, check the :ref:`doc_list_of_classes_and_documenters`. Try to work
- on classes not already assigned nor filled.
- This file is produced by Godot Engine. It is used by the editor, for
- example in the Help window (F1, Shift+F1).
- You can edit this file using your favourite text editor.
- Here is an example with the Node2D class:
- ::
-
- Base node for 2D system.
-
-
- Base node for 2D system. Node2D contains a position, rotation and scale, which is used to position and animate. It can alternatively be used with a custom 2D transform ([Matrix32]). A tree of Node2Ds allows complex hierachies for animation and positioning.
-
-
-
-
-
-
- Set the position of the 2d node.
-
-
-
-
-
-
- Set the rotation of the 2d node.
-
-
-
-
-
-
- Set the scale of the 2d node.
-
-
-
-
-
-
- Return the position of the 2D node.
-
-
-
-
-
-
- Return the rotation of the 2D node.
-
-
-
-
-
-
- Return the scale of the 2D node.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Return the global position of the 2D node.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- As you can see, some methods in this class have no description (i.e.
- there is no text between their marks). This can also happen for the
- description and the brief\_description of the class, but in our case
- they are already filled. Let's edit the description of the rotate()
- method:
- ::
-
-
-
- Rotates the node of "degrees" degrees.
-
- That's all!
- You simply have to write any missing text between these marks:
- -
- -
- -
- Describe clearly and shortly what it does. You can include an example of
- use if needed. Avoid grammar faults.
- I don't know what this method does!
- -----------------------------------
- Not a problem. Leave it behind for now, and don't forget to notify the
- missing methods when you request a pull of your changes. Another
- editor will take care of it.
- If you wonder what a method does, you can still have a look at its
- implementation in Godot Engine's source code on GitHub. Also, if you
- have a doubt, feel free to ask on the
- `Forums <http://www.godotengine.org/projects/godot-engine/boards>`__
- and on IRC (freenode, #godotengine).
|