alexanderjcs / multiplayer-sudoku Goto Github PK

Add a timer next to the game ID that will show the hours until the room times out

socket.io takes a long time to load (300 ms - 1 second or so). We could instead:

1. Load the webpage with an empty board
2. Load socket.io asynchronously
3. When socket.io loads, establish the connection and set up the event listeners
4. Continue operation like normal

Which would reduce the perceived wait time for the user, since the webpage has loaded.

The player configuration color picker is on a different line in Chrome

What it should look like:

The current location of each user's cursor is shown by a highlighted box. There will be a key of each box color and the person's name on the right-side of the screen.

Currently there is a hard-coded cap to only pencil in 5 numbers. I propose making a newline after 5 characters and allowing up to all 9 numbers

Visual improvement: "Game ID" should be bold but the actual game ID itself should not (in this case, "abc")

Database entries for different difficulties of the same puzzle seem to be the same

Players should receive 10 points when they enter a correct number. They have 10 points remove a number, and 5 points removed if they enter an incorrect number

A readme needs to be created.

Will contain information on how to install, develop, as well as put into production.

Also will include screenshots, and a link to a live server once created

Add a client-side checkbox to hide the notes.

Front-end code needs to be split into multiple files desperately.

Add the option for different color themes. An extension of issue #1.

This application needs an easy-to-use config file that contains the server port and IP that the websocket client should connect to.

Sudoku puzzles need to be randomly selected from a database (to make sure that there is little time needed to actually create the puzzle).

What needs to be done:

1. Create the SQLite (or maybe NoSQL?) database containing ~1000 easy, medium, hard, expert, and insane difficulties (names can be decided on)
2. Read from that database when creating the Board class

Self explanatory. Happens client-side but not server-side.

Likely an input sanitization issue.

Check some TODO messages in app.py for potential security vulnerabilities:

# TODO: Add the SECRET_KEY configuration to the app object.
# TODO: security vulnerability - check the message before broadcasting it to all clients.

Mobile support can be easily added by double-checking the scaling and adding a bunch of buttons from 1-9 (and a backspace)

Sometimes socket.io can't connect to the server and it hangs on "Connecting...". This is rare and not reproducible, but is quite annoying when it happens. This is solved by refreshing the page.

If socket.io doesn't receive a connection event within a few seconds, the frontend should try refreshing the page.

Self explanatory. Makai is probably working on this