abell95 / galaga_invaders Goto Github PK

Initialize requisite objects in main.rb:

• ship
• fort
• alien
• ufo
• big alien

Update to have print statements for game state.

"bullet" is not in the domain language for this project. Func spec uses "missile." Additionally, this is overly specific. With this convention we would need alien_bullet.rb as well, which seems redundant and not adherent to DRY.

Need a method (probably a class) that can track the timing for everything in the game.

Start creating and implementing Alien subclasses, possible removal of ufo file

Create class for managing instantiation + position tracking of missiles, among other things

The readme filename for this project repo should be capitalized ("README.md").

Contain the duplicated logic between wave, wing and squadron

Create stub class for the core game state (tracking if game is over, points, etc.)

The 'Wave' class manages alien movements, level completion, and alien waves and squadrons.

Appears that methods are inconsistent.

Extend missile and integrate with missile collection.

Create base logic for bullet class - which represents the bullets the player ship fires

Focus on "update"

Add team member names to the README so rich VCs know who to pay off

The name of the file is different from the class within.

Add the basic top-level logic for the movement and firing mechanisms of the player class

Create Fort class to represent ingame forts, implement basic logic to avoid compilation errors

Specificity in class name is potentially restrictive. If this class was extended or inherited by another, the name would be misleading since the player does not control any other actors in the system. Specificity is important, but probably not at the cost of flexibility and tolerance to change. I propose that the player.rb aka player_ship.rb be renamed to ship.rb.

Originally posted by @bmchristensen in #9 (comment)