board results and transition to cardstories 2.0 client

The invitation pick mockup was integrated. The cardstories 2.0 showcase now runs on the cardstories 1.0 server and both can be used simultaneously. The django authentication release candidate was merged into the master branch.

board result

The board displayed during the invitation phased was moved to the invitation_board_* functions. There were no common functions between all the invitation state beforehand. But the new mockups show much more common elements.
The display of the game state is grouped in a separate div for each state, as it previously was. However, the chat room is common to all and moved out. In order to show a display consistent with the mockups, the chat room is positioned in absolute. The blocks in a given state are arranged using blocks and margin instead of absolute positioning because it matches the mockups.

.cardstories .cardstories_chat {
    position: absolute;
    height: 500px;
    width: 180px;
    right: 0px;
    bottom: 0px;
    border: 3px solid black;

release candidate 1.0.6

The release 1.0.6 release candidate contains cherry-picked backward compatible protocol modifications to make it forward compatible with the upcoming 2.0.

It was installed at

cardstories 2.0 client on 1.0.6 server

The cardstories 2.0 showcase was running on its own modified server. With the 1.0.6 release installed, it was reconfigured to run on the default cardstories server. The new client can be used to watch over games being played with the old client on the same server.

$.cardstories.url = '/cardstories/resource';


django authentication

A large changeset was merged into the master branch with django authentication support. A few minor issues were identified to make it useable: