GameInterface

See the Game Interface Section of the User Guide for a description of the current user interface.

We chose not to use the Twitter Bootstrap framework for this project as the nature of our interface did not conform to what the framework offered. Specifically, the framework tries to resize and rearrange content based on screen size, which would be problematic for our implementation, which relies on elements remaining in the same place (Wrapping elements in the page causes an undesired interface). Moreover, the framework uses fixed (fixed percentages) spacing between elements, resulting in wasted space.

###Future Implementations: ####Change Game Phase Indicator Currently, a green arrow exists, allowing users to indicate that they are ready to move to the next state. There should be another icon to let a player know that the opposing player is ready to move on, and is waiting for them to acknowledge.

####Card State Overlay Each card should be able to change it's background color based on its state. For example, a card that was successfully activated during the Generation Phase would have a green background, while a card with a failed activation would have a red background. This also helps keep track of which cards have activated this turn.

####Card Context Menu Each card should also have a context menu (activated by a double click) that allows various actions, such as:

• Discard (Removes the card from the game)
• Bid (Allows a user to secretly bid on a card)
• Activate (E_Gen & Service cards only. Simulates a dice roll, and changes the card background accordingly. This could also update a user's points.)
• Attach/Detach (Allows a user to drop another card on this card and bind the two or Allows a user to separate two joined cards)

#####Card Bid Overlay During the Bidding phase, users would select the card they wanted to bid on and submit a bid for that card. Upon entering the Reveal step, the system would reveal both bids via an overlay, and give control to the winning user. The overlay could simply be two numbers representing the bids, with player1's bid at the top and player 2's bid at the bottom.

####Chat Feature A chat feature would be beneficial to help user communication. The chatbox could be located on the right, taking the place of the opposing player's hand field (and shrinking the deck menus).

####Server Communications The system should also check in with the server every few seconds via an AJAX request, and change the field state accordingly.

A “GameInterface” wiki page providing annotated images documenting the (final version of the) interface to the system using Twitter Bootstrap and (perhaps) DivShot. (Create a directory called images/ at top level, push your image files there, then display them in this page.)