Zmiany
/* Files to download */
===Discussion of solutions to selected module II additional tasks===
'''Time to complete this part: about 15 minutes''' <br/>
::''At the beginning of the lesson we remind students what they were supposed to prepare between classes. We invite a volunteer to present his/her solution. We discuss with the students if anyone solved the task in a different way. We discuss the solutions (we praise each correct solution to a task).'' <br/>
::''If there was no homework, we start by reviewing key issues from the previous module. We also ask if students have any doubts about their own projects. If any students want to, we let them present something they are proud of.'' <br/>
===Designing a game involving going through a maze===
We begin the discussion of how we should describe the behaviour of the character (sprite), and how we are going to control it: <br/>
'''Question:''' With what should the game start after it is initiated? <br/>
:::''There may be various suggestions. We should prompt the students that our character should be placed in the middle of the starting square. It should be noted that the sprite character should entirely fit in a single maze square, so as not to touch its walls.''
'''Question:''' How will we control the character? <br/>
:::''What button are we going to use to make our character go forward? Should it move forever?'' <br/>:::''– We guide the students to find the answer “No,” because it will collide with a maze wall.'' <br/>
:::''How many steps should it now take?'' <br/> :::''– Enough to move from one square to the next, adjacent one. We discuss what this means, pointing to the maze drawing on the board. Together we reach the conclusion that the character should move forward a number of steps that is equal to the length of the side of a single field in our maze.'' <br/>
:::''In this case, should we choose to control the character with the computer mouse or the keyboard?'' <br/>:::''– In this game it will be easier to control the character using the keyboard.''<br/>
:::''After discussing which key should make the character move by one square, we write on the board what we have agreed on, for example:''<br/>:::'''* ''When the up arrow key is pressed, go forward by “one square.''”'''
'''Question:''' How should the computer react if the character collides with a maze wall? <br/>
:::''There will be various answers, such as: the character dies, the game starts from the beginning, etc. We hint that if we do not want the game to end too quickly, it will be enough for the character to bounce off the wall and return to its previous place. Additionally, it can emit a sound, e.g. meow.'' <br/>
:::''We add the following to the previous record, e.g.'' <br/>:::'''''* If the character collides with a wall, go back to where it was previously located, and then: '''''<br/>:::'''''* Play a meow sound''.'''<br/>
'''Question:''' How can we rotate the character, so that it walks in a different direction? <br/>
:::''There will be various suggestions. We write down one of them on the board.
NOTE: At this point we discuss how the character is to move (up, down, left, right). We explain how it can rotate. We remind the students of how we drew a square in the first module and rotated the sprite by 90 degrees to the left or right. We guide the students towards a solution where the character is rotated left or right.'' <br/>
:::''After discussing which key should control the character, we write on the board what we have agreed on, for example:'' <br/>:::'''''* When the right arrow key has been pressed, rotate the character by 90 degrees to the right.''''' <br/>:::'''''* When the left arrow key has been pressed, rotate the character by 90 degrees to the left.''''' <br/>
'''Question:''' What should happen when the character reaches the exit? <br/>
:::''We discuss how the game is to end. Let our hero make a sound and display the word “Exit!” in a speech bubble. This is the end of the game, so we should stop all scripts.'' <br/>
'''We ask the following question:''' Which of the above tasks can we already accomplish? <br/>
:::''– Move the character (we do not yet know how far the character is to be moved)'' <br/>:::''– Rotate the character 90 degrees to the left or right by pressing a given key'' <br/>:::''– Change the stage background. '' <br/>
'''We ask the following question:''' What do we have to learn? <br/>
:::''– How to recognise that the character has walked into a wall, i.e. a prohibited stage area, or reached the exit'' <br/>:::''– How to move the character backwards, i.e. reverse it'' <br/>:::''– How to play sounds (unless we have introduced this command earlier in class or as homework / an additional task).'' <br/>
===Preparation: recognition of the background colour by the sprite===
We explain that at the beginning we will learn to recognise if the sprite has entered a square of a certain colour, i.e. is it touching a given colour. <br/>
'''Task:''' We ask the students to double click the stage or the stage icon located in the bottom left corner. <br/> ::''We remind them that the appearance of the screen changes, and in the top centre of the screen we can go to the Background tab to change the stage.''<br/>
[[Plik:maze3.JPG|center]]
We then ask the students to double click the sprite located on the stage or to choose its icon in the lower left part of the window and go to the Scripts tab. <br/>
::''We explain that this way we go back to creating sprite-related scripts. We explain that this way we can switch between defining the stage characteristics and the sprite.''<br/>
'''Task for self-completion:''' We ask students to build and test three sprite control scripts: <br/>
* The third should rotate the sprite left by 90 degrees when the ''left arrow key'' is pressed.
::''We allow students a few minutes to complete the task. Depending on the group we may remind the students which blocks should be used to build scripts. We check if everyone managed to create the scripts.'' <br/>
[[Plik:maze4.JPG|center]]
'''We explain''' that after the sprite has entered the red square we want it to go back by the same number of steps, i.e. return to where it was. <br/>
'''Task:''' We ask students to try and find a block (blocks) to check whether the sprite is touching a specified colour. If necessary, we help them (e.g. suggest that it is among sensors). <br/>
::''Students should find a few blocks. Among them, the is '''touching colour'''? Block. If necessary, we briefly discuss other blocks and explain why they are not going to work in this case.'' <br/>
[[Plik:maze5.JPG]] <br/>
<br/>
::''We reach the conclusion that it must move. We ask by how many steps. By as many as it moved forward previously. We wonder about which block we should use for movement – we have only one. But in it we can enter the number of steps which the sprite is to add (i.e. move forward). How to put down that now it is to go back? We reach the conclusion that we should subtract the number steps by which the character moved forward. That’s why we enter them with a minus.'' <br/>
[[Plik:maze7.JPG]] <br/>
'''We ask the following question:''' Where should we place these instructions? <br/>
::Together with the students we think about where the instructions should be placed. We should come to the conclusion that the script '''when <up arrow> key is pressed''', which causes the movement of the character, needs to be modified because only when the character moves can it enter a forbidden colour. <br/>
[[Plik:maze8.JPG|center]] <br/>
[[Plik:maze14.JPG|center]]<br/>
::''We discuss whether the word should be displayed continually or only for a moment. That is why we select the block with the display time – '''say... for 2 s'''.'' <br/>
'''Task for self-completion:''' We ask the students to add to the walk script instructions that cause a reaction to the sprite’s reaching the blue square, i.e. the exit. We discuss where to put them. We hint that the structure should be similar to the one used to check whether the sprite reached the colour red. <br/>
::''We allow some time to complete the task, then ask one of the students to show a solution on the interactive whiteboard, and check whether everyone has solved the task.'' <br/>
[[Plik:maze15.JPG]]
'''Task for self-completion:''' We propose that students change the script so that pressing an arrow key sets the character in the direction of the arrow and moves it by 40 steps.<br/>
[[Plik:maze22.JPG|center]] <br/>
===Suggested homework (task for self-completion)===
'''Additional task for self-completion:''' We suggest that students add a new maze background by copying the existing one and then editing it (by colouring the respective squares red or green). <br/>
Then they should modify the script in terms of what should happen when the character reaches the exit: <br/>
::– a background change has taken place (we can use the block '''change background to <background name>''' and select the '''next background''' from the dropdown list), <br/>
::– the sprite has returned to the starting point (NOTE: in the case of the new stage the starting point may be different than previously, but it is easier to keep the same one). If the starting point is always in the same place, the game can be played indefinitely without the need to add other modifications in the scripts (after passing all the boards the player will return to the first one). If the game is to end after the player has passed two or more boards, the last board should be identified as such (e.g. by the background name). <br/>
==Files to download==
[[Plik:maze_Plansza1.png|300px|file1]]
[[Plik:maze_Plansza2.png|300px|file2]]
