http://scratch.mit.edu/projects/23685408/
I thought this project was challenging because I thought I would have the solution to something but it turns out that the project did not pick it up. This was frustrating and I felt like I was sort of going in circles but I eventually figured whatever I did wrong out and was able to fix it. This unit was interesting but I did not enjoy it as much as learning about things we are going to be using later in life such as HTML codes or how to use the Microsoft Office programs.
Carolyn's Computer Apps Blog
Wednesday, June 18, 2014
Monday, June 16, 2014
Scratch Final Project
The purpose of my game is to get the bat to eat the little beetles and avoid the fox. If the bat touches the fox, 5 points are taken off of the score. When the levels advance, there are different sprites but the same objective. However, in each level up, there is another sprite that will take points off of your score.
Tuesday, June 10, 2014
Monday, June 9, 2014
Friday, June 6, 2014
Debug It! Week 3
3.1
http://scratch.mit.edu/projects/23298182/#player
3.2
http://scratch.mit.edu/projects/23298299/#player
3.3
http://scratch.mit.edu/projects/23298517/#player
3.4
http://scratch.mit.edu/projects/23298905/#player
Reflection:
I thought these challenges were the most interesting yet and I enjoyed doing them.
http://scratch.mit.edu/projects/23298182/#player
3.2
http://scratch.mit.edu/projects/23298299/#player
3.3
http://scratch.mit.edu/projects/23298517/#player
3.4
http://scratch.mit.edu/projects/23298905/#player
Reflection:
I thought these challenges were the most interesting yet and I enjoyed doing them.
Thursday, June 5, 2014
Debug It! Week 2
2.1
http://scratch.mit.edu/projects/23246899/#player
2.2
http://scratch.mit.edu/projects/23247013/#player
2.3
http://scratch.mit.edu/projects/23247391/#player
2.4
http://scratch.mit.edu/projects/23247559/#player
2.5
http://scratch.mit.edu/projects/23247683/#player
Reflection:
I think these were interesting and similar to the debug it challenges in week one.
http://scratch.mit.edu/projects/23246899/#player
2.2
http://scratch.mit.edu/projects/23247013/#player
2.3
http://scratch.mit.edu/projects/23247391/#player
2.4
http://scratch.mit.edu/projects/23247559/#player
2.5
http://scratch.mit.edu/projects/23247683/#player
Reflection:
I think these were interesting and similar to the debug it challenges in week one.
Debug It! Week 1
Debug It 1:
Since both Gobo and Scratch Cat are supposed to dance but only Scratch Cat does, you have to click on Gobo's sprite icon and see if there is a command, "When the green flag is clicked" at the top of the commands listed in the designated space. If not, put one there and it should work.
http://scratch.mit.edu/projects/23245827/#player
Debug It 2:
In order for the project to loop, you have to make sure that there is a command that sets it back to the original space. If you don't have this, you are going to have Scratch Cat in the ending place when it loops again. To fix this, you should put a "go to x:__, y:__" command at the beginning with the coordinates of wherever Scratch Cat starts off for it to loop correctly.
http://scratch.mit.edu/projects/23246045/#player
Debug It 3:
Make sure that the command "When space bar is hit" is in the list of commands instead of a command like "When green flag/this sprite is clicked".
http://scratch.mit.edu/projects/23246193/#player
Debug It 4:
Take out any commands that tell the sprite to turn a certain amount of degrees. If you don't already have commands like "glide to x:__, y:__" with the coordinates you want it to go to, add those in and it should be fixed.
http://scratch.mit.edu/projects/23246341/#player
Debug It 5:
Put a repeat command around the "say meow" command. Also you may want to put a "wait __ seconds" before the speech bubble command.
http://scratch.mit.edu/projects/23246591/#player
Reflection:
I think some of these Debug It challenges were interesting and made you think about all the factors that goes into programming a computer.
Since both Gobo and Scratch Cat are supposed to dance but only Scratch Cat does, you have to click on Gobo's sprite icon and see if there is a command, "When the green flag is clicked" at the top of the commands listed in the designated space. If not, put one there and it should work.
http://scratch.mit.edu/projects/23245827/#player
Debug It 2:
In order for the project to loop, you have to make sure that there is a command that sets it back to the original space. If you don't have this, you are going to have Scratch Cat in the ending place when it loops again. To fix this, you should put a "go to x:__, y:__" command at the beginning with the coordinates of wherever Scratch Cat starts off for it to loop correctly.
http://scratch.mit.edu/projects/23246045/#player
Debug It 3:
Make sure that the command "When space bar is hit" is in the list of commands instead of a command like "When green flag/this sprite is clicked".
http://scratch.mit.edu/projects/23246193/#player
Debug It 4:
Take out any commands that tell the sprite to turn a certain amount of degrees. If you don't already have commands like "glide to x:__, y:__" with the coordinates you want it to go to, add those in and it should be fixed.
http://scratch.mit.edu/projects/23246341/#player
Debug It 5:
Put a repeat command around the "say meow" command. Also you may want to put a "wait __ seconds" before the speech bubble command.
http://scratch.mit.edu/projects/23246591/#player
Reflection:
I think some of these Debug It challenges were interesting and made you think about all the factors that goes into programming a computer.
Subscribe to:
Posts (Atom)