-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rewrite the step_by_step series #4325
Rewrite the step_by_step series #4325
Conversation
e789e71
to
35711fa
Compare
The first part, nodes_and_scenes.rst, is ready to review. |
68bb690
to
f1eb377
Compare
The instancing page is ready to review |
1ef68f4
to
2cf7eb1
Compare
The scripting languages page is ready to review. |
f8fe03b
to
72cbef9
Compare
Added the hands on scripting tut. It's lacking images but it's late here so I'm about to tap out. I'd like to get a read and people to tell me if the amount of detail is fine, that is, neither too little nor too much for a broad audience like people who read the Godot docs. Thinking about accessibility, I ended up putting quite a lot of details and notes despite the code's simplicity in the hope to better explain how game code and a gdscript file work. Note: while the final page will provide C# code tabs, the focus is still on GDScript. There's no way around focusing on one language and its specifics in these kinds of tutorials. To offer the same experience to people learning with or C# or even visual script, I think we'd need separate pages so the text or media can explain the specificities of each language. The docs:
|
b952392
to
404d146
Compare
Just added images and polished the scripting part. I'm going to edit and clean-up some old content as a bonus and then the last page left for this PR is the signals intro. |
@akien-mga for this PR and its parent PR #4302, what do you think of merging them to get user reviews? It's hard for the target audience to come and review the series on GitHub. Once merged, I could share the series with the community, in particular, new Godot users so they can go through it and report any issues or questions they have. Saying that because I tried sharing the PR and some documents and got feedback from few users, although it's positive so far. |
e3f149f
to
f03eefa
Compare
Okay the content's kinda there. Ready to review. |
f03eefa
to
e8807ee
Compare
Added two pictures and minor edit, now it's done done! |
NB: I'll move remaining content that shouldn't be in the series in other PRs, like #4344 |
.. note:: The Godot team can't provide an open-source console export due to the | ||
licensing terms imposed by console manufacturers. Regardless of the | ||
engine you use, though, releasing games on consoles is always a lot of | ||
work. You can read more on that here: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing link 🙃
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you review the intro in its PR? It's #4302. This PR is just based on it because there are links to the intro, but 4302 should be reviewed and merged first.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, this is confusing...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated the first message to reflect that. I just split the work into two PRs hoping the other would get reviews and merged while this one was a draft.
.. image:: img/introduction_helms_of_fury.jpg | ||
|
||
As for applications, the open-source pixel art drawing program Pixelorama is | ||
powered by Godot, and so is the voxel RPG creator RPG in a box. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should product names be formatted with italic maybe? RPG in a box looks especially blended into the sentence.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same remark, this is the intro, see #4302. Note I'm taking note of these comments.
Thanks for taking the time to review! |
Agreed, I'm sorry I've been the bottleneck for so long here. Needs a rebase now that #4302 is merged, then we can merge. |
620c5a9
to
de33fa3
Compare
This is a complete rewrite and merge of instancing.rst and instancing_continued.rst. The goal was to simplify the language and unify the tutorial around the falling ball. Some instructions are more detailed than in the original article. There are also more pictures, all new, and using yellow outlines for color-blind people. Closes godotengine#4175 Closes godotengine#4171
The page now focuses on giving an overview of official scripting languages. Removed first example using signals. We'll introduce signals later in the series. Moved the explanation of what scripts are and do to the top, before talking about languages. Mentioned other things like that GDScript isn't like Python, that it's an imperative and OO language, with links to wikipedia that explain the jargon. Closes godotengine#4172
97bbb39
to
15b02ec
Compare
See #4302 first, which is the PR for the introduction section. This second builds upon it so #4302 should get reviewed and merged first.
Closes #2459
Closes #1664
Closes #1663
Closes #1510
Closes #1001