Improve Klondike tutorial
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
Locate the Klondike tutorial and review parts 4, Gameplay, and 5, Additional features, against the complete code shown at the end of each part. Check where the instructions, Run and Code buttons, and warnings are unclear; done means the tutorial can be followed with clearer step boundaries and functional results.
Written by the indexing model from the issue text.
Description
What could be improved
Feedback on the Klondike tutorial from moluderu on Discord:
I tried to compile my feedback on the tutorial I nearly finished. It took me about 12-15 hours, I didn't really count.
Right now, if I follow the tutorial exactly as it's written, I end up with an application that doesn't work at all. It's missing pieces and it's full of errors. With the full code at the end of each part, I was able to improve my code to bring it up to standard, but it's essential to do so and this button isn't really highlighted in the tutorial. I think it would be a good idea to use the "Run" and "Code" buttons more often throughout the tutorial.
If you do as I do, you'll end up with clean, functional code after all.
A few small warnings about deprecated stuff like "event.delta" or ".forEach" but, on the whole, it works well.
Overall, the tutorial would benefit from being more injunctive: being clearer about "you MUST do this" or "it's ALREADY been done".
To be a little more precise, I'd have to say it's well written, but there are a few areas that need a bit of work.
In part 4.Gameplay, there's a lack of detail, but it's an advanced stage of the tutorial, so it's not a problem - it just helps to see if you've followed the instructions correctly.
On the other hand, in the last part, 5.Additionnal features, there are quite a few things that are difficult to follow with the large blocks of text and code. The author seems to assume that we have the complete code in front of us at the same time and can directly see what he has written. But the complete code is at the very end of the page and I have to say that I'd rather do things myself than read code comments. This part gave me trouble and I find the rest of the tutorial much better. Sorry for the author, I don't mean to be rude, I'm trying to give constructive criticism.
I've got as far as the "A New World" part for now and it's getting really difficult for me to continue. I'm finding it hard to move on at the moment, I don't seem to understand anything any more. I think I'll go through the documentation a bit and try a few things for fun before coming back to this.
Why should this be improved
To make it an easier time for our users to learn Flame.
Any risks?
No.
More information
- Dominant language
- Dart
- Stars
- 10.8k
- Forks
- 1.1k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 61
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from flame-engine/flame
-
Timer with tickCount stays finished after start() or reset()Possibly taken @matthewalberto claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
flame-engine/flame#4240 · 1 comment ·
Maintainers usually reply within 1 day
-
`CameraComponent.follow` follows the local position of a nested targetPossibly taken @ufrshubham claimed this 1 day ago. Openbug
flame-engine/flame#4238 · 1 assignee ·
Maintainers usually reply within 1 day
-
`ComponentPool` returns components to the pool while they are still in use, and loses components removed before mountingPossibly taken @ufrshubham claimed this 18 days ago. Openbug
flame-engine/flame#4191 · 1 assignee ·
Maintainers usually reply within 1 day
-
Move the flame_studio debugging features to flame_devtoolsPossibly taken A pull request linked to this issue is open or already merged. Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
flame-engine/flame#4176 ·
Maintainers usually reply within 1 day
-
discussion enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
flame-engine/flame#4175 ·
Maintainers usually reply within 1 day
All issues in flame-engine/flame
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
spotiflacapp/SpotiFLAC-Mobile#935 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
chriskelly/wish-together#193 ·
Maintainers usually reply within 1 day
-
area: player feature request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100