gilday / clue-less Goto Github PK

Nothing is preventing players from moving around the board however they wish and then updating the server. Very easy to cheat

By default the IP address of the server defaults to 10.0.2.2 because this is what the android emulator understand to be the host machine's ip address. Should the user choose to do a different P address, the next time they launch the app, this address will reset to 10.0.2.2. Ideally the app should remember the last address used in SharedPrefernces or some other persistent storage

We're implementing our own transformations from "Ball Room" to "ball_room"
Google's Guava library can simplify this and a host of other things for us

http://code.google.com/p/guava-libraries/wiki/StringsExplained#CaseFormat

While in the game, there needs to be a notification area to tell the user what has just happened.

The GSMatch objects that come back from the server should have a new "message" value each time something has happened in the game. This should be the message to display to the user

Ideally, we could keep track of all the messages and put them in a list like a log so users can see what happened in the last 3 turns if they have been away from the game for a little while. Consider this part an enhancement on the necessary notification

At the beginning of a match, pawns for each player should be on the board on their start spaces adjacent to the hallway. The only reason I know where to move Ms Scarlett is bc I've been doing this every night for weeks ;)

If everyone starts their app and logins in to the match, then players start taking turns, everything works fine.

If you log in to the match and take your turn, then another player logs in to the match, this new player will not receive the right updates

When the user leaves the game, the background thread that is polling the server should be stopped. Ideally, this would be a proper Android background service that could display notifications and always run even when the user isn't looking.

As we discussed in class when we talked about user interfaces, menu systems should only make available those actions which the user may select.

Our game board is a menu system. It presents possible choices to the user and the users selects one. The game board should make it clear that the user may only select the spaces their pawn may move to.

Use the GameBoard's getPossibleMovesForPlayer method to get a list of possible navigations and do something in the UI to highlight these while clearly disabling invalid navigation chocies

The GameBoard class will report that a user is able to move from the hallway back to their start space. This should not be allowed. Can only move from start space to hallway

When the Android service serialized the GSMatch to JSON, it would treat the custom match state (ClueMatchState) as a String and therefore would sanitize it thus ruining the JSON structure. This has been resolved and we are now posting with pure JSON.

This raises another bug. Rails will deserialize the whole JSON object, including the custom match data field, and then try to persist this object. When it puts the deserialized match data into the column, it looks the result of a to_s on a Ruby object is stored and is useless to us.

Try to change the match data hash back to JSON before dumping in a column

http://benatkin.com/2011/11/07/json-column-coder/

There is nothing preventing players from moving out of turn. When it is not a player's turn, UI widgets like "end turn" and gameboard spaces need to be disabled.
Likewise, the backend logic should prevent this behavior even if the GUI fails to prevent this