For this phase, we had very strict deadlines and guidelines that were established to finish the project for the day immediately following the 28th after class.
A couple of things changed throughout the course of our design phase and through the implementation phase. We omitted the thought process of having two classes to use for the GameInput class and combined it into a single class.
We also thought that there should maybe be a mouseclick event to interact with the page on things that could not be inputted through the keyboard. This was omitted when we started implementing the project as we deemed it unnecessary to the overall design at that point and to some extent was deemed out of our use case for this project.
From our design phase, we each had our classes that we established to start working on. The GameScore class was established by Matthew as a Singleton. This piece was responsible for methods that manipulate the score of the game. The GameScore class also uses the Constant class to calculate scores, which he also established. Ola established a time frame for our project and initially put together some questions for implementation as well as implementing the InputDebouncer. I was set to establish the GameInput, but after some deliberation, I had trouble implementing it within the 24 hour time frame to finish the project on Friday. Ola helped implement this with use of Tetrino class.
A lot of this deliberation and class design was established through our discussion on our group slack page for Team Bravo Tetris. During implementing our design, we also decided against the click listener. A lot of the overall implementation in terms of architecture was established by Bryce, our team lead, as he helped guide us on pieces that deemed unnecessary or incoherent with our design.
This part of the project was finished in record time on Saturday within the 24 hour time frame established.
-Ellen E
No comments:
Post a Comment