c2vi / fsst-battleships Goto Github PK

this task no longer includes any message handling

• make a class Player, of which an object is created, when ever a player connects. and added to the player Dict

• this Player class holds things like the player_id, the connection obj, player_name.....

• it gets all those things passed to the constructor

• has a method: set_name(name), to set the name of the player

• the handle_socket() is a function outside of the Server Class.

• gets the following params: handle_socket(server_obj, player_obj)

• and is run in another thread (which it already is)

• the handle_message(server_obj, player_obj, message) gets those params

branch: prototype-client

• read the stream line by line, and parse each line as a message

branch: server-start
store each client-socket, the name in a dict and give them an id

• that id is then also the key in the dict
• also a variable for the next free id to give to the next connecting client

• the client message handling

• make a Client class (name: Client, file: client/main.py)

• that listens for messages from the server and calls methods from the Gui Main Window class

• and exposes methods, to interact with the game, for the Gui class to call

• run the window (main gui class) in another thread

in server/main.py every conn gets set as self.conn, so when a new client connects, his connections overwrites the one from the old client.

branch: handle-msg

add the switch over all message types in handle_message()

When the server receives a message that is not valid json, then send back an error msg with the message: "what you sent was not valid JSON", and print "received a message that was not valid JSON"

branch: client-gui
file: gui/matchmaking.py, gui/main.py

• gui/main.py should be a wrapper widget, and a function, that starts the window, so that we can add header bars or something like that in the future
• field, for inputing the name, and button to call an set_name() function in main.py
• do if name == "main": in gui/main.py, so that you can run the window for testing (with some test data as well)
• expose methods for the Client class to call, when it recieves messages from the server

add a game class in a file server/game.py which stores the state of a game, and has methods to get this game-state and do things to the game.

improve (or add a way) the way code from the handle_message accesses game state (like the list of players)
make a method for all the things the handle_message function has to do (for that go through the proto.md file)

eg: a method for getting the list of players: get_player_list()
and dfinetly one to send a message to another player: send_to_player(player_id, msg)

parse the config.toml file into a python dictionary

branch: parse-toml

• use tomllib
• add tomllib to requirements.txt
• docs: https://docs.python.org/3/library/tomllib.html