This line can be simplified from:
`If installing Visual Studio 2017 or 2019, make sure to enable **C++** in
the list of workflows to install.`
To:
`Make sure to enable **C++** in the list of workflows to install.`
This line is not needed as we don't support 2015 anymore:
`If installing Visual Studio 2015, make sure to run a **Custom**
installation instead of **Typical** and select **C++** as a language there.`
This can be simplified from:
`If you've already made the mistake of installing Visual Studio without
C++ support, run the installer again; it should present you a **Modify** button.`
To:
`If you've already installed Visual Studio without C++ support, run the installer
again; it should present you a **Modify** button.`
From my checking on my system, this line is no longer true, so we can remove it:
`Running the installer from *Add/Remove Programs* will only give you
a **Repair** option, which won't let you install C++ tools.`
Now we can move the simplified text up so that the reader does not have to dig through the entire document to find that important bit of information, while not making the text at the top much longer due removing outdated information.
This allows users to leave comments on pages that don't have
`:allow_comments: False` somewhere in the page's source.
Both manual and class reference pages can receive comments.
Index pages cannot have comments, as discussion should occur on "leaf" pages.
GitHub Discussions is used as a backend on the same repository. This means
that Discussions *must* be enabled on godotengine/godot-docs before this
commit is merged to `master`. Users can choose to use the "Custom" watch
mode if they don't want to get notifications for discussion updates,
but still get notifications for issue and pull request updates.
User comments are intended to be used for the following purposes:
- Add a clarification or correct something in the documentation,
without having to open a pull request. Contributors are encouraged to
take a look at discussions from time to time, and see if there's information
worth incorporating in the pages themselves. Don't forget to reply to
the comment when doing so :)
- Mention a workaround for a common issue.
- Link to useful third-party resources that are relevant to the current page,
such as tutorials or add-ons.
User comments should *not* be used for technical support. Other community
platforms should be used for that.
Page-to-discussion matching is done using the `pagename` Sphinx variable,
which is independent of the Godot version and documentation language.
Being independent of the Godot version allows keeping old comments
when the Godot version changes, while also allowing users from `/stable`
and `/4.1` to "see" each other in discussions.
See https://giscus.app for more information.
This isn't strictly related to compiling custom export templates,
but it's a neat trick to reduce the final distribution size that works
regardless of the export template binary used.
The document suggests copy `/usr/lib/libatomic_ops.a` to
`/usr/lib/libatomic.a`. Instead of copying, using a soft link to
libatomic_ops is also an option. The reason to soft link is also added.
I have successfully built Godot by using soft link.
Fix outdated environment variables when setting up MinGW-w64 paths. Also
add a note to mind different host/target architectures (common pitfall
when compiling from e.g. Apple silicon).
Co-authored-by: Hugo Locurcio <hugo.locurcio@hugo.pro>
I noticed some of the phrasing and grammar in object_class.rst was a bit confusing, so I tried to improve the clarity while keeping the original intent of the content.
Let me know if the changes are consistent with the rest of the docs, thanks!
The path to the `bin/` directory is written from the root as `./bin/<godot_binary>`,
however the path to the `scripts/` directory is written from outside the root as
`godot-source/modules/gdscript/tests/scripts`, which is inconsistent.
melquiadess