Updated README

README.md

 # source-rasp
 
-Source code for the foosball embedded Raspberry PI. It runs the UI and manages games.
+Source code for the foosball embedded Raspberry PI.
+It runs the UI and manages games.
 The UI is done with PyQt5.
 
 ## Dependencies
 * PyQt5
-* pyserial
-* autopy
+* pyautogui
 * qtmultimedia5-examples
 
 ## Launch
 * Make sure to have Python>3.5 installed (`sudo apt-get install python3` otherwise)
 * Make sure to have PyQt5 installed (`sudo pip install pyqt5` otherwise)
-* Compile the .ui and .rc files: `./compile_resources.sh`
-* Execute main.py: `python3 main.py`
+* Compile the .ui and .rc files: `./devtools.sh ui`
+* Execute main.py: `python3 babyfut.py`
 
 ## Edit the UI
 The UI is mostly created using Qt-Designer:
 * Download qt4-designer (`sudo apt-get install qt4-designer`)
 * Edit .ui files with qt4-designer
-* Compile the .ui in a python file: `./compile_resources.sh`
+* Compile the .ui in a python file: `./devtool.sh ui`
 * Done!
 
 ## Sofware Organisation
 ### UI
 The UI is only made of one window with static widgets and changing "modules".
-There are currently 3 modules:
+There are currently 7 modules:
 * Main menu, showed on startup and giving access to other panels
 * Game, containing the scores, timers, etc of the current game
-* Options, to allow the user tp configure some options
-* Authentification for two players
-* ...
+* Leaderboard, for comparing players scores, times, etc + delete itself from the database
+* Options, to allow the user to configure some options(language, max score, etc)
+* Authentification for 2 to 4 players in party mode
+* Authentification for n players in league mode
+* Endgame, giving the winner(s) and storing results in the db
 
 Those inherit from the `Module` class and are composed of 5 things:
 * Access to the main window, through the `parent_win` member
@@ -44,6 +46,11 @@ The widget contained by each module are stacked in a QStackedWidget and only one
 To get from one to the other, the current module is unloaded current, then the new one is shown and loaded.
 Each module can overload the load/unload/other method in order to have a specific behavior.
 
+### Threads
+In addition to the main UI thread, there are 2 other threads running:
+* Input, managing buttons control, rfid reading and goal detection
+* Replay, capturing video during a match and storing it when there is a goal
+
 ### Settings
 Settings are stored in a JSON file located in the parent's `content` directory, that looks like:
 ```
@@ -95,12 +102,23 @@ Settings['ui.fullscreen'] = False
 duration = Settings['replay.duration']
 ```
 
-### Replays
-Replays are 5-10 seconds clips played when a goal is scored. Those are stored in the parent's `content` directory under the name `replay0.mp4` and `replay1.mp4`.
-For the time being, those are provided by the PI camera module.
+Note that for potential security reasons, this file is not synchronized with git, but is downloadable on the PR's GDrive
 
-### DB
+### Replays
+Replays are 5-10 seconds clips played when a goal is scored. Those are stored in the parent's `content` directory under the name `Replay Left.mp4` and `Replay Right.mp4`.
+Those are provided by the PI camera module, thanks to another thread that records the video while a game takes place and stores it once a goal is marked.
 
+## DB
+The database is currently in SQLite but should be transposable to MySQL later on. There are 3 tables:
+* Players: Storing player information (name, rfid, etc)
+* Matches: Storing matches start/stop times and winners/losers
+* Teams: Linking players and matches
 
 ## Todo
-* [ ] Add the possibility to stop the replay mid-video by pushing any button
+* [ ] Check validity of replays on a real rasp
+* [ ] Check validity of rfid on a real rasp
+* [ ] League mode
+* [ ] Translation on the fly (instead of having to manually restart)
+* [ ] Installation guide
+* [ ] Connection to another PI to exchange RFID and videos
+* [ ] Integration of the real UTC DB