Available
Apr 6, 2022 at 8:05am - Jun 3, 2022 at 11:59pm
This assignment was locked Jun 3, 2022 at 11:59pm.
Lesson 15: Keyboard Input
Question of the Day: How can our programs react to user input?
Following the introduction to booleans andifstatements in the previous lesson, students are introduced to a new block calledkeyDown()Links to an external site.which returns a boolean and can be used in conditionals statements to move sprites around the screen. By the end of this lesson, students will have written programs that take keyboard input from the user to control sprites on the screen.
To earn credit for the lesson, students will submit a screenshot of their bubble 6. The screenshot should show:
The student's code for the level (specifically the conditionals)
The animation it creates
The animation should do what is required in the directions and uses a conditional (show in your screenshot).
For a distinguished score, students have all the requirements above and have:
Added a second sprite that move from TOP to BOTTOM while ROTATING
Added a third sprite that moves from LEFT to RIGHT while ROTATING
Submit a shared link to the animation (see below)
Additionally, since we'll be using animations starting now, please share the link to your project by clicking the share button, copying the link, and pasting it in as a comment for your submission.
164931479904/06/202211:59pm
Rubric
true
57258
Can't change a rubric once you've started using it.
• Work correctly uses previously learned concepts, code, or materials not explicitly required in the directions.
• Code executes correctly, with no errors, and correct output.
• Work shows independent thinking.
• Work shows a genuine effort to understand and creatively apply the topic or material.
• Answers (if required) are written in complete sentences.
• Code (if required) is organized and formatted for readability (uses whitespace and indentation to separate elements, appropriate names, etc)
• All sections of the assignment are complete.
• Code executes correctly, with no errors, and correct output. • Work shows student thinking, regardless of “correctness”. • Work shows genuine effort to understand the topic. • Answers (if required) are written in complete sentences. • Code (if required) is formatted for readability (uses whitespace and indentation to separate elements, appropriate names, etc) • All sections of the assignment are complete
• Code executes, possibly with errors, generates an expected output that is close to the correct output. • Work shows an attempt to understand the topic. • Work demonstrates student thinking, but needs expanding or clarification. • Answers (if required) are in fragments or incomplete sentences. • Code (if required) is hard to read • Some sections of the assignment are incomplete.
• Portions of the code run, but contain many errors or is incomplete.
• The code output is severely incomplete or broken
• No evidence of student thinking.
• Answers are attempts to “fill space” or do not make sense.
• Answers are fragments or incomplete; difficult to read
• Aspects of the task incomplete or missing
• Code is broken, incorrect, or incomplete, resulting in no output. • Work is missing or plagiarized from another website • More than half the assignment is blank or incomplete • Work has a complete heading
Find Rubric
