Thank you for these proposals for beta tests.
I do not plan to use this type of activity with my grade K10 to K12 students. I prefer to use the current version of Blockly by providing functions to simplify the code if necessary. The principle with scenes is enough for me if I wish to have progress in stages.
However, I also create activities for grade K1 to K9 students. I would be interested to be able to create by myself activities with a simplified interface.
Some remarks on this new interface proposed in these two activities:
- I would prefer that this interface does not move away unnecessarily from the usual interface of CoSpaces: navigation in the scenes at the bottom, button run at the top right, … It would facilitate the transition.
- The idea of the instructions for each scene is very interesting and could be generalized in CoSpaces.
- The Help and Continue buttons should be really fixed. A real HUD is missing in CoSpaces.
- A block can easily be moved: it is very good but it’s a pity that this is not the case in Blockly.
- A trash can be added for students who do not understand how to delete a block.
- In Robot rattle, the symbols “clockwise” and “countrary clockwise” are reversed and the time out blocks the proper functioning.
- It would be interesting for the teacher or even the students to easily modify the proposed mechanisms to create their own stages (and the corresponding code).
My students have just returned from a two-week vacation. I proposed this week to my grade K11 students to test these two activities (independently, at home). A student (Quentin H.), who knows CoSpaces well, has already finished the Pirate plunder and gave me his feedback on this activity:
"The negative points :
We sometimes have up to 4 to 5 audio tracks that start at the same time, moreover, they are not interresting and too repetitive.
- Loading time
You have to wait every time you press a button. Even at home with a broadband connection it takes 1 min to charge the scene at the beginning. The time to start each test really disrupts the process of the student who wants to test the behavior corresponding to different versions of his code. I understand why the title is “hour-of-code” …
- Too repetitive
It’s usually always the same at every step of the activity. I understand why it was done like that, and I have no way to improve it.
The positive points:
- Solutions are given
When the student fails to take a step, he may have the solution.
- Integrated help
For “complex” blocks help is offered. Of course, it is only really useful if it is translated into the student’s language.
If you come to the end of the activity you can get a wonderful diploma. But if we click on the last step of the activity, we also have the diploma