We must bind the player selection activity to the model. The activity must:

• Be able to create new players, and hold them in a list.
• Edit (while the user is inside the activity) the name and skin of the player.
• Click "Play", and thus pass information to the GameActivtiy, or even add the information to a currently existing game.

To integrate the custom board themes and player skins in the interface.

Define facades for the model and the gamemodel. That is, define how the subsystems can communicate with each other.

Reuse the code from the borrowed project, and make it work in our app

What is it exactly?

Music will "pop" when changing acitivies fast, this is beacause onResume and OnPause are being called constantly

Wait isn't this a simple fix?

Not really, we need to really fix the killing activities and then is a matter of a simply check of isFinishing

Sometimes we still don't kill activies when we should.

There are two solutions, either try to fix it directly, or blocking the ability to play with the same skin, which is in my opinion the best option.

We must implement the Theme Selection Activity. It must:

• Display ALL the themes, differentiating amongst the purchased and unpurchased ones.
• Show which theme is currently selected.
• Change the selected theme by clicking on it's corresponding image/button.

For some reason the app name is initAcitivity when it should be CustoPoly

Pues eso, está casi todo hecho pero no tengo ni idea si funciona (primera vez que hago lo de xml con ese parser y escribir/guardar archivos en java). Así que cuando este todo hecho y compile esto queda pendiente :D

Implement the communication between the activities and the model?

Implement the shop activity as it is in the mockup. It must:

• Display all the themes, marking which are purchased and which aren't (maybe reuse the code from ThemeSelectionActivity?), and their cost.
• Give the player the ability to buy a theme (el cómo ya es cosa del implementador. Sugerencia: al clickar en un tema no comprado, que salte un diálogo de yes/no con "Want to buy this theme?" Para ejemplo, mirar el AskBoyCommand, que hace algo muuuy parecido).
• Display the points the player has.

The imlpementor of this part must:

• LOOK at the Commands part of the model to figure out what he needs.
• Implement the game logic (AKA the necessary calls to the game object, external commands if necessary, etc.) NOTE: I think that the buy, sell and mortgage buttons are implemented via dialogs in the reused source code, so they can be deleted.

The implementor must:

• Find out a way to display the state of the game in the activtiy (aka the board), show where each player is and the theme. Basically, just fill out the big gray space in the mockup.

This is the right half of the GameActivity. It must:

• Display how much money all players have at any given time.
• Implement a button that displays the properties owned by the current player (el que está jugando su turno). This is a list from the Player object.
• DO NOT implement the "End turn" button from the mockup.