Embedded Files
Wednesday, June 5 :: Click Link for assignment >
Call for TOT Entries!!! Website Design :)
Call for TOT Entries!!! Website Design :)
Did you create a website (Last Quarter) and want to compete? Please join Ms. Eamigh for a meeting on (TODAY) Thursday, February 8 during lunch!
Fill out the form to get a 5star pass (pick up your lunch first then come to room 102!)
The day of the tournament, students must as a team of 2-3, build a 1 (one) page website to show their skills! (PS...you got this!!!)
Expectations:
Expectations:
C: Voice Level 2 (only the people next to you can hear you and no shouting across the room)
H: Ask your team, elbow partner or raise hand
A: Work on the assignment
M: Stay in your assigned seat
P: Work till assignment is completed
S: Finishing your work
Take a moment to check ATLAS!
Take a moment to check ATLAS!
Grades are in for Lesson 5! Did you finish?
Grades are in for Lesson 5! Did you finish?
If you did not finish Lesson 5, Page 8!
Make sure to complete it now!!!!
IDK is NOT the correct answer. Incomplete will be given if the levels (green and purple dots) are not shown and the answer to #8 isn't finished!!!
Sequential Programming: the program runs by itself!
Event Driven Programming: the user MUST interact with the program (like click!)
Typing.com ASSIGNMENT!
Typing.com ASSIGNMENT!
Intermediate: Intermediate Punctuation
Due Friday, February 9
STOP at Intermediate Punctuation!
STOP at Intermediate Punctuation!
Do NOT begin Quick Sentences!
Do NOT begin Quick Sentences!
If you go past this lesson it will be reset!!!
If you go past this lesson it will be reset!!!
Typing:
Typing:
Log in to typing.com
Click Lessons
On Intermediate Tab, Click Intermediate Punctuation
Due Friday, February 9
10 Pts.
If you are finished or waiting, work on Clever!
If you are finished or waiting, work on Clever!
Students click on the Clever icon on the desktop
Sign in using the username & password (same as logging into computer)
Click on the square that says iReady
Continue until time is up!
Lessons have been assigned to them based on their diagnostic test results both in Math and Reading. Within each lesson are brain break games. The district is pushing a goal of 45 minutes per week on Online Lessons in ELA and 45 minutes per week in Math to close the gaps found in the diagnostic. Math and ELA are providing some of that time during the week, but not all.
PLEASE DO NOT GO AHEAD ON CODE.ORG... THERE ARE ADDITIONS TO IT TODAY!
Wait for instruction!
WHAT ARE WE LEARNING: App Development....Debugging!
WHY IS IT IMPORTANT: Investigating working code continues to be an introduction to many of the skills of programming. Students are also introduced to debugging as a skill they'll need to use and develop as programmers. A huge goal of this lesson, however, is attitudinal.
Students will be able to (SWBAT):
Debug simple sequential and event-driven programs
Use the debugging process and Identify specific best practices for debugging programs
Use the speed slider, break points, and documentation as part of the debugging process
HOW WILL MY TEACHER KNOW WHAT I LEARNED: You will learn how to identify and fix problems and answer a follow up question!
No matter what level of experience - everyone gets bugs! And with a little practice everyone can get good at debugging. Find out the 4 simple steps it takes to squash a bug and some tips to debug even faster...
ASSIGNMENT: Debugging!
ASSIGNMENT: Debugging!
25 Points!
25 Points!
Click on CODE.org
Once on your DASHBOARD...
Scroll down to find CLASSROOM SELECTIONS
Select:
Unit 3-Intro to App Design
YOU WILL START:
Lesson 6: Debugging
As you follow along in the lesson, you will use a form to answer the questions from the lesson! (below)
Click 1 to begin
PAGE 1:
Do This:
Debug this program.
Try This: Notice the slider at the bottom of the screen? Currently the speed is set to "turtle". This slows down the running of your program, so you can watch each step and debug.
If you flip the code from block to text mode, you can see the code highlighting as it's run. This is a form of a visualizer, a tool software developers use to help visualize code and find bugs.
Let's Debug line 2
Add quote marks around the word green in line 2
Did it work? Why?
Click RESET...RUN the program
If you do NOT complete the work...
PAGE 2:
Do This:
Debug this program.
First...Run the program!
Try This: Look at the Debug Console at the bottom
What is it telling you is wrong?
Let's Debug line 4
Add quote marks around the word blue (click the arrow for the drop down menu) in line 4
Did it work? Why?
Click RESET...RUN the program
Page 3:
Do This:
Run this program to see how it works.
Debug the program so that the smiley face does not go off the screen.
This has to do with RANDOM NUMBERS
Correcting page 3
Hover over the white area in the app
Look at the X and Y coordinates.
X is horizontal (left to right)
Y is vertical (up and down)
How far is too far?
Try this:
For the Random Number on Line 3...change 400 to 250
For the Random Number on Line 4...change 500 to 350
Run the program! Did it work?
Page 4:
Don't put onEvent blocks inside other onEvent blocks. You almost never want to.
Do This:
Run this program, hit the up button, play the music, then stop the music, and hide the controls.
Do you notice something weird happening this second time?
Why you think this is happening
Debug the program to fix the issue you found.
Page 5:
Hunt For The Bug 🐛
Your classmate needs your help. They wrote this program meant to make it so that when you click each a button, that button gets bigger and the font changes. But there's a bug and the program doesn't work as it's intended.
Read through the following program, seeing if you can find where the bug might be. After discussing the following questions with your partner, write down your predictions and run the code to see what the program does.
You must answer the questions...
What will happen when you run this program and click on one of the buttons?
What advice would you give to the person who wrote this program so that they can avoid this type of bug in the future?
STOP HERE TODAY!
TOMORROW...
PRACTICE DEBUGGING: YOU MUST COMPLETE ALL 3!
FARM SOUNDS:
Do This:
Run the app to see how it works
Debug this program to use the correct sound and text when the user clicks each animal
CLUB FAIR APP:
Do This:
Run this program to see how it works.
Add code to the program so that the "Go Back" button takes the user back to the home screen
MOOD MINDER APP:
Do This:
Run this program to see how it works. Then add code to the app to make the "Excited" button work.
Pick a song, image, and text to show when the button is clicked
Make sure only the "Excited" button has a thick border when it's clicked
You can use the code for the other buttons for ideas on how to write the code
TIP: We will need to google and save an image!
Also...Is the note on line #1 correct? What is wrong? Fix it!
Debugging Strategies
Keep your code clean
Use clear, meaningful IDs for your elements
Keep your code organized in chunks that do the same thing
Use comments to explain your code
Write code using blocks
Run your code
Run your code a lot, every time you add a command or two
Slow down your code with the speed slider. Watch how it runs closely
Use console.log to get output. Add extra output statements throughout your code to get feedback on what parts are running.
Use classmates and resources
Talk out the problems with a partner or classmate
Compare your code to examples that you know work
Read documentation to know how a block is supposed to work
Hand trace your code to track what's happening.
VOCABULARY
Documentation: a written description of how a command or piece of code works or was developed.
Comment: form of program documentation written into the program to be read by people and which do not affect how a program runs.
PAGE 7: (Reflecting on Programming)
What is one thing you really enjoyed about today's activity?
Is there anything that you found confusing or need extra help with?
From what we have learned, answer the question IN YOUR OWN WORDS on level 7.
IDK or blank answers will not be accepted!
Completing the code.org assignment is worth
25 points!
NOTE: MAKE SURE THE TOP OF THE CODE.ORG LESSON SHOWS THAT IS COMPLETE! (ALL CIRCLES ETC SHOULD BE GREEN!)
Remember, if you skip a page this will occur:
REMEMBER!
Each section will be checked for completion!
(the work MUST be done on each level!)
Page updated
Google Sites
Report abuse