Improve Klondike tutorial

Abierto
  • ¿Algo no está bien?
#2,917 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
dart, flutter
Área
documentation

Línea de trabajo

Localiza el Klondike tutorial y revisa las partes 4, Gameplay, y 5, Additional features, comparándolas con el código completo mostrado al final de cada parte. Comprueba dónde las instrucciones, los botones Run y Code y las advertencias no son claros; el trabajo estará terminado cuando el tutorial se pueda seguir con límites entre pasos más claros y resultados funcionales.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

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

Lenguaje dominante
Dart
Estrellas
10.8k
Forks
1.1k
Merge medio
1 d 22 h
PR fusionados (30 d)
54

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de flame-engine/flame

Todos los issues de flame-engine/flame

Issues similares

Más issues de Dart

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.