Updated TODO

master
Aadhavan Srinivasan 7 months ago
parent f3dcbc3b3e
commit 3bf65ab8f9

@ -1,14 +1,10 @@
1. Sign Windows executable, to remove 'Unknown Publisher' warnings. 1. Sign Windows executable, to remove 'Unknown Publisher' warnings.
2. Add 'install' target to Meson, to allow the user to install the game. This should also copy the .so files to the right locations. 2. Add 'install' target to Meson, to allow the user to install the game. This should also copy the .so files to the right locations.
3. Use free() to free allocated memory. 3. Use free() to free allocated memory.
4. Use check_client() and check_server() for CLI invocation as well, and pass a flag that indicataes whether the parameters were entered through GUI or CLI (also probably create a function to handle printing vs. GUI display). 4. Use the struct to establish a connection, and to start each round (instead of sending strings).
5. Use the struct to establish a connection, and to start each round (instead of sending strings). 5. Figure out how to build statically-linked Mac binary, and create a build script for packaging it.
6. Figure out how to build statically-linked Mac binary, and create a build script for packaging it. 6. Communicate the paddle reset position to the peer, after a round.
7. Communicate the paddle reset position to the peer, after a round. 7. Clean up / refactor the raygui code in main.cpp, that asks user for game mode. Instead of just having a giant blob of code in main.cpp, maybe split it into a function, or move it to another file. It should be easy to split it into a different function, since none of the functions take any specific parameters. The text box function, for example, only takes in the rectangle coordinates, and the text to display. I can move the code to a function, and then pass in any parameters that I need to pass in (I don't think I need to pass many parameters, though).
8. Clean up / refactor the raygui code in main.cpp, that asks user for game mode. Instead of just having a giant blob of code in main.cpp, maybe split it into a function, or move it to another file. It should be easy to split it into a different function, since none of the functions take any specific parameters. The text box function, for example, only takes in the rectangle coordinates, and the text to display. I can move the code to a function, and then pass in any parameters that I need to pass in (I don't think I need to pass many parameters, though). 8. Allow the user to specify which paddle they want to control, in multi-player mode.
9. Allow the user to specify which paddle they want to control, in multi-player mode. 9. Try to make the ball go between screens.
10. Try to make the ball go between screens. 10. Change the networking code, so that a single server can connect two clients with each other. The server should provide player 1 with a code, and player 2 can connect with player 1 using that code (essentially like a room).
11. Change the networking code, so that a single server can connect two clients with each other. The server should provide player 1 with a code, and player 2 can connect with player 1 using that code (essentially like a room).
12. Add a --help option, that displays information about the game and how to run it.
13. Add better error-checking to check_server() and check_client() (Use check_server_client() as inspiration).
14. Ensure that check_server() and check_client() work properly for command-line invocation, then remove check_server_client().

Loading…
Cancel
Save