• This includes cutthroat, static, templates, and cutthroats.py. Change any paths/setup as required.

Create a Connection class in db2 similar to db and move existing object classes inside that class.

tornado-nginx-example.conf
How can I set up a Tornado server to run behind nginx?

We'll just not parse the command line for now.

starter.db should not contain any entries, only tables with columns as required for operation.

The API currently doesn't seem to be letting us call "/api/room/listplayers" from "/room/game". This list should be displayed in the UI, as discussed in the wireframes.

We should fetch and cache Bootstrap and other scripts currently fetched from CDNs locally on our server, and serve them ourselves. Could set up a periodic callback or something to fetch them, but can also just do it manually.

Need to add settings with all the links the fetch from; default settings can be where we fetch from currently. Then just need to modify the pages to hit the files with static_url.

Can check if user is logged in by getting self.get_current_user(); if it comes back empty, raise, otherwise, return a 200 telling user they are already logged in.

Should only be present if user is logged in? You can check if the user is logged in by hitting /api/auth/login with a GET request; if you get back a 200, they're logged in, but if it's a 403, they're not (for this to work though, issue #32 must first be completed; additionally, logout route needs to be implemented, #31 ).

Front-end should sha512 passwords before sending to API. Doesn't necessarily have to be sha512; can be anything so long as we stick to using it.

• Move ctconfig inside cutthroat package
• Make a config folder and move cutthroat.conf inside that (change paths in install.bash etc. as required)

There is a lot of undocumented code in the API; make sure to not only write/update docstrings for functions/methods/classes but also lots of in-line comments (be sure to update those). In-line comments are good!

Currently we just raise an alert; we can do something pretty with bootstrap and pass through the errors from the API.

I think we should probably do this once we have almost all the functionality down.

some style guides (will add more later):
https://drupal.org/node/1720586

It would be effective user-feedback to have tooltips appear in the UI for instructions for newcomers. We might also be able to implement them in the Game Page when a ball has been sunk. Tooltips are included in Bootstrap's tooltip.js

Should return something like:

[{"name": "room1", "pwd_required": false}, ...]

This is the most important feature of this whole app after all haha.

• Define setting here: https://github.com/hfaran/LivesPool/blob/dev/ctconfig.py
• Add the same default here: https://github.com/hfaran/LivesPool/blob/dev/cutthroat.conf
• Grab and pass the option when setting a new cookie here: https://github.com/hfaran/LivesPool/blob/dev/cutthroat/api/auth.py#L40

@io_schema decorators need to be before @authenticated as they verify output and it is NoneType on redirects.

We need to properly implement API error handling on the lobby page. See TODO's in roomlobby.js

The room pages (lobby and in-play) should have the room names displayed as the page and banner titles. We will implement this from the server-side.

• After authenticating, if a player is not in a game, they will be forwarded to /views/room/join, otherwise if the player is in a game, the player will be forwarded to the current game screen. A "landing page" of sorts can provide the redirection (i.e., just logic in a requesthandler that either redirects to game screen if user is in a game, or room joining screen otherwise)
• There is currently no way to exit a game other than to join a new room; there should be an explicit button on the game screen to leave the game and only then will the player be allowed to browse other rooms. (Also, a new route needs to be added that implements leaving the current game for a player)

This should be fairly easy; just need to remember the set of balls from the beginning and put the ball back in the same column as before.

Selenium with Python

Implement a search bar at the top of the Join Rooms Page, before the list of rooms.

When in the view /room/lobby, the user has the option to exit from the current room lobby. This action should make the same API call, with logic in the backend to determine if the game should be retired, or if the player should just be removed. This way, the front-end can simply POST this action regardless of the user being an owner or player in the room.

Currently using divs that form balls, arranged in a right-angle triangle. We should prettify it by creating some graphic designs and using images instead, then arranging them in the proper equilateral triangle shape.

Add list of rooms to the Join Room Page. If list is empty, we should populate the Join Room Page with a "create room" button that redirects to the Create Room Page.