oriolagobat / filler-game Goto Github PK

• SelectorStub
• Functional selecto

Timer

• updateTimer(int newValue)

View should have a timer (a textView maybe) drawn on the screen which is able to change it's value through the above method.

GameResponse

• handleGameResponse(GameRespone response)

I shouldn't matter if the response comes from a pressed button, from the GameOrchestrator due to round timeout or if it is the response
to the IA choosing a color.

We should investigate if there's any edit Text variant in Material Design three more interesting than the classic one.

• Let the user upload or take a picture to use as pfp
• Two player mode
• Make song resume from where it was
• Fix landscape selector spacing

If I understood corretly, we won't be able to do this as we had planned, as intent data and bundle data can only be a Uri, not a class instance

• Landscape
  • #30
  • #31
• #53
• #40
• #33
  • Refactor music player / stopper function into shared
• #34
• #35
• #36
• #32
• #39
• #41
• #37
• #38
• #52
  • #49
  • #50
  • #51
• #54
• #55

This is a list of the main features to be implemented on the configuration of a new game:

• Alias for player (player name)
• Number of colors (from 3 to 8)
• Grid length (always square, from 3 to 9)
• Time control
• Difficulty

• We should be using this library if we are looking for a better grade
• We should also stop using linear layout to do the application, changing them into constraint layout's

• Player
• #12
• Round
• Game
• #13
• #10

List of things we may consider implementing if we have enough time:

• #24
• Refactor configuration file
• #23
• Make sure to check the game stack
• #19
• #18
• #25
• #20
• #16
• #17
• #27
• #26
• #28
• Close the game when exit button pressed on result screen

We should also think what to do with the background.
As of now, it looks quite nice, although maybe it makes it so that we can't see the text quite well.

List of files in which we must implement extra data savings in case the game suffers a restart:

• Configuration screen
• Game screen
• Results screen

On screen, user gets the difficulty with the first capital letter and the other letters underscored.
However, on constants, difficulties are tagged with all capitals.

Should we:

• Change constants to be first letter capital and rest underscores?
• Parse it to all capital in the GUI ?

To fix this, we'll need to modify line 43, and parametrize it depending on if it's the board grid or the selector one, to do the square root of all the items or return just the number of items. Steps to follow:

• Implement constants class GridType, which will have Board and Selector
• Implement parametrization of this type, and pass the required one upon call
• Refactor line 43 of GridAdapter.kt, by making it:
  • Return the square root if it's the board grid
  • Return the number of total items if it's the selector grid

Should showing the date to the user be the gui job, or the logic one?