Difference between revisions of "IB Computer Science 1"
From WLCS
(→Monday - Wednesday (5/23/16 - 5/25/16)) |
|||
Line 17: | Line 17: | ||
** [https://www.quia.com/quiz/1865016.html Practice WRS Test] | ** [https://www.quia.com/quiz/1865016.html Practice WRS Test] | ||
* Integrating Brickbreaker - collisions & brick drawing | * Integrating Brickbreaker - collisions & brick drawing | ||
+ | * If you have not already done so, demonstrate brick collisions for credit | ||
* Demonstrate a working Brickbreaker game for credit | * Demonstrate a working Brickbreaker game for credit | ||
** All bricks collide and disappear to win | ** All bricks collide and disappear to win |
Revision as of 08:21, 25 May 2016
Contents
- 1 Monday - Wednesday (5/23/16 - 5/25/16)
- 2 Monday - Thursday (5/9/16 - 5/19/16)
- 3 Tuesday - Thursday (5/3/16 - 5/5/16)
- 4 Friday (4/29/16)
- 5 Monday - Wednesday (4/25/16 - 4/27/16)
- 6 Tuesday - Thursday (4/19/16 - 4/21/16)
- 7 Tuesday - Thursday (4/12/16 - 4/14/16)
- 8 Monday - Friday (4/4/16 - 4/8/16)
- 9 Archives
Monday - Wednesday (5/23/16 - 5/25/16)
Agenda:
- Internal Assessment: Criterion A: Planning
- Internal Assessment
- Media:IBCS_InternalAssessmentChecklist.doc
- IA Criteria Rubrics
- IA Examples
- Criterion A Overview - due Friday (5/27/16) via Google Classroom
- Explicitly state your client
- Explicitly state your advisor
- Define and describe the problem or unanswered question (175-250 words)
- Justify your proposed product (175-250 words)
- List (bulleted sentences/phrases) your success criteria (functionality requirements)
- Workplace Readiness Skills Assessment - Friday (5/27/16)
- Common-sense workplace questions
- 1 hour - 100 multiple choice
- Practice WRS Test
- Integrating Brickbreaker - collisions & brick drawing
- If you have not already done so, demonstrate brick collisions for credit
- Demonstrate a working Brickbreaker game for credit
- All bricks collide and disappear to win
- Ball passing the bottom of the screen loses
Monday - Thursday (5/9/16 - 5/19/16)
- Complete the NVCC Course Evaluation survey
- Complete the CTE Student Survey
- Brickbreaker intro
- Draw a row of bricks w/ a for loop
- Draw multiple rows of bricks by adding another for loop
- Give each brick a random color (if you want the colors to stay the same throughout the game, then you'll need arrays)
- Brick collision detection - demonstrate the collision testing once completed for credit
- Create a new sketchbook just to develop your collision detection
- You will develop 4 different functions to check if a ball collides with the different sides of a brick
- Declare and initialize all the variables for a ball -- start your ball at the top of the screen and have it go straight downwards
- Declare and initialize brick_x, brick_y, brick_w, brick_h variables
- Declare and initialize a boolean visible variable, which is true -- this variable will remember if a brick is visible or not. If the brick is hit, then we set it to false
- Define a function named boolean checkTop(int brick_x, int brick_y)
- if the ball's bottom edge (ball_y+ball_r) is greater than the brick's top edge (brick_y) AND the ball's bottom edge is still less than the brick's bottom edge (brick_y+brick_h) AND the ball's left edge (ball_x-ball_r) is less than the brick's right edge (brick_x+brick_w) AND the ball's right edge (ball_x+ball_r) is greater than the brick's left edge (brick_x)...then the ball must be hitting the top edge and you should return true
- otherwise, return false
- Go to the draw() function
- Draw and move your ball
- if visible is true, then
- Draw the brick
- Check if the ball has hit the top of the brick by using an if-statement and checkTop(brick_x, brick_y)
- If the brick is hit, then set visible to false and flip the direction of the ball
- If you get checkTop() working, then change the starting location and direction of the ball and develop checkLeft(), checkRight(), and checkBottom()
- Demonstrate the collision testing once completed for credit
Tuesday - Thursday (5/3/16 - 5/5/16)
Agenda:
- Complete the NVCC Course Evaluation survey
- Complete the CTE Student Survey
- Convert and demo Lab 6 / 7 (Tic-Tac-Toe)
- for loop review and practice
- Write a for loop that prints 0 to 10 by 2s
- Write a for loop that prints 25 to 175 by 25
Friday (4/29/16)
Agenda:
- Complete the NVCC Course Evaluation survey
- Convert and demo Lab 6 / 7 (Tic-Tac-Toe)
Monday - Wednesday (4/25/16 - 4/27/16)
- AB/IB testing absence survey
- Convert and demo Labs 4, 5, and 6 in Java (unless 6 is combined with your 7)
- Intro to Java arrays and for loops
- Convert and demo Lab 6 / 7 (Tic-Tac-Toe)
Tuesday - Thursday (4/19/16 - 4/21/16)
- Java Review
- Convert Lab 4: Simple Paint from Python->Java syntax. Demo for credit
- Convert Lab 5: Ping from Python->Java syntax. Demo for credit
- Convert Lab 6: Tic-Tac-Toe from Python->Java syntax. Demo for credit
- Lists/Arrays are handled slightly differently in Java
Tuesday - Thursday (4/12/16 - 4/14/16)
Agenda:
- Grades are updated in Synergy (3rd quarter ends Thursday/Friday)
- These are your final grades for 3rd quarter unless you demo something missing for partial credit
- Demo Lab 7: Tic-Tac-Toe (Part 2)
- Introduction to Java syntax
- Python -> Java differences
Monday - Friday (4/4/16 - 4/8/16)
Agenda:
- Demo missing assignments
- Two-dimensional lists (matrices)
- Work on Lab 7: Tic-Tac-Toe (Part 2)