troygnichols / chessoid Goto Github PK

When you move a chess piece, you must first touch the piece you want to move ("select" it), and then the tile on the board you want to move it to. That's fine, but the currently selected piece (the one that's about to move) should be differentiated somehow.

My first thought is that it should blink slowly like a cursor. Find a way to do this. Maybe the Animation class from Android can help? This will probably be implemented in ChessoidMain.moveTo, when we are setting the clipboard, if a user clicked on a chess piece.

Down the road, this will need to be implemented. As a refresher: http://en.wikipedia.org/wiki/En_passant

Re-orienting the phone causes the screen to be re-drawn (portrait or landscape or whatever Android calls it), and that calls the ChessoidMain.onCreate() method. We need to either prevent the redraw on a tilt or have ChessoidMain maintain state when onCreate is re-called (it might re-draw, but it puts the pieces back where they were).

Minority opinion: it's not a bug but a feature. This feature enables more realistic gameplay, as when real-life chess boards are turned on their sides, the pieces do indeed fall off the board and the players are forced to restart.

Chess rules need to be updated to make sure pieces can't move through each other.

Castling is not really supported in the current incarnation of the chess engine. Add some functionality so the engine can tell if a castling move will be allowed or not.