Clarifications and terms concistency

Open
#41 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Start with the linked page, getting_started/step_by_step/scripting_first_script, and find where _process(), _input() and _unhandled_input() are called 'virtual functions' and where they are called 'callbacks'. The issue does not say which term to keep, so agree on one with a maintainer first. Done means the tutorial pages use that single term consistently, or clarify it once where the two terms first meet.

Written by the indexing model from the issue text.

Description

Redot: 26.1

The documentation uses several different terms to describe the same concepts, which makes it confusing for beginners.
For example, the tutorial refers to _process(), _input(), _unhandled_input(), etc. as “virtual functions” in one section, and later calls them “callbacks” without explaining that these two terms refer to the same concept.
Using multiple names for the same mechanism without clarification creates unnecessary confusion. It would help if the documentation consistently used a single term.

https://docs.redotengine.org/getting_started/step_by_step/scripting_first_script#complete-script

Dominant language
C#
Stars
4
Forks
7
Avg merge
6h 10m
Merged PRs (30d)
4

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Redot-Engine/Redot-Documentation

All issues in Redot-Engine/Redot-Documentation

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.