Prg2/flappy dot - ประวัติรุ่นแก้ไข

Jittat: /* Objectives */

2021-03-11T00:51:10Z

Objectives

2021-03-11T00:50:56Z

Objectives

2021-03-11T00:50:20Z

Objectives

2021-03-11T00:48:24Z

Merge your work

2021-03-11T00:40:23Z

2021-03-11T00:37:19Z

Collisions and game control

2021-03-11T00:36:11Z

The pillar pair

2021-03-11T00:32:54Z

Collisions and game control

2021-03-11T00:31:06Z

Merge your work

2021-03-11T00:25:02Z

Changes in gamelib

@@ แถว 17: / แถว 17: @@
 '''Your assignment:''' For today, you do not have to complete the project (but if it is fun, you should).  You are required to start working on the project with your teammate.  Each of you would work on a different feature on a different git branch.  After each of your work is done, you should merge them into the main branch of the shared repository.
-You should submit the URL of your shared repository.  (Form will be available soon.)
+You should submit the URL of your shared repository.  (The submission form will be available soon.)
 }}

@@ แถว 16: / แถว 16: @@
 {{กล่องฟ้า|
 '''Your assignment:''' For today, you do not have to complete the project (but if it is fun, you should).  You are required to start working on the project with your teammate.  Each of you would work on a different feature on a different git branch.  After each of your work is done, you should merge them into the main branch of the shared repository.
 }}

@@ แถว 13: / แถว 13: @@
 * basic game programming
 * how to apply object-oriented programming concepts to game development
 === Task breakdown ===

@@ แถว 442: / แถว 442: @@
 If you encounter merge conflicts, look at the conflict closely.  It might be just that you edit different things at the same place and you can just accept all changes.
 When you finishing manually merging changes, you should commit your work.  Don't forget to "add" the conflicted files before commits.  If you can't work things out, please call the TAs.  Don't call "--force" to get things done because you might be likely to destroy your own work.
-[[Image:Prg2-flappy-merge-conflict.png]]
+{{กล่องฟ้า|
 == Developer 1 - Player falls off the screen ==

@@ แถว 455: / แถว 455: @@
 * Move the cards you work on to "In progess" column and move them to "Done" column when you are done
 * Start working in a branch, commit regularly, and merge your work to the main branch when you are done
 }}
@@ แถว 473: / แถว 475: @@
 * Move the cards you work on to "In progess" column and move them to "Done" column when you are done
 * Start working in a branch, commit regularly, and merge your work to the main branch when you are done
 }}
@@ แถว 495: / แถว 499: @@
 * Move the cards you work on to "In progess" column and move them to "Done" column when you are done
 * Start working in a branch, commit regularly, and merge your work to the main branch when you are done
 }}

@@ แถว 508: / แถว 508: @@
 ** The Dot is of size 40 x 40.
 * You might check the collision in FlappyApp <tt>post_update</tt> and stop the game when the collision occurs
 == Towards a complete game ==

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 00:36, 11 มีนาคม 2564
แถว 366:		แถว 366:

	=== The pillar pair ===		=== The pillar pair ===
		+
		+	We will use a single sprite for the top and bottom pillars, hence the name: pillar pairs. The sprite image contains both pillars with the hole in the middle. When it shows, the top and the bottom of the pillars are clipped as shown below.
		+
		+	[[Image:Clipped-pillars.png]]

	Let's create <tt>PillarPair</tt> class.		Let's create <tt>PillarPair</tt> class.

@@ แถว 499: / แถว 499: @@
 Implementation tips for collision detection:
-* Add method <tt>is_hit</tt> in Dot that takes the pillar pair and checks if the Dot hits the top or the bottom pillars.
+* To checks if the Dot hits the top or the bottom pillars, either (1) add method <tt>is_hit</tt> in Dot that takes the pillar pair, or (2) add method <tt>is_hit</tt> in the PillarPair that takes a Dot.
 ** It would be easier to check the x-coordinate and the y-coordinate separately.
 ** The position x and y of the pillar pair is at the empty center of the pair.  The pillar width is 80 pixels and the empty space in the middle is of height 200 pixels.

@@ แถว 435: / แถว 435: @@
 == Merge your work ==
-You should merge your work into the main branch.  Since both of you work on the same file, it can be the case that git would find conflicts in your edits.  Don't worry about that, because it is fact of life.
+At this point, you should merge your work into the main branch.  Since both of you work on the same file, it can be the case that git would find conflicts in your edits.  Don't worry about that, because it is fact of life.
 If you encounter merge conflicts, look at the conflict closely.  It might be just that you edit different things at the same place and you can just accept all changes.
 When you finishing manually merging changes, you should commit your work.  Don't forget to "add" the conflicted files before commits.  If you can't work things out, please call the TAs.  Don't call "--force" to get things done because you might be likely to destroy your own work.
 == Developer 1 - Player falls off the screen ==

@@ แถว 57: / แถว 57: @@
 * New initialization methods: <tt>init_element</tt> for Sprite and Text, and <tt>init_game</tt> for GameApp
 * GameApp update methods: <tt>pre_update</tt> and <tt>post_update</tt> which would be called '''before''' the updates of all elements are called and '''after''' they are called.  These two methods will be very useful when we want to handle global events such as collisions.
 == Basic player physics ==