Registration via the logger
A new user should be able to register using the logger.
When the logger is first run (i.e. no config file found, i.e. the PID is unknown), it should display a message asking the user if he/she wants to register.
If so, a dialog box should be displayed asking for the data needed for the registration. This dialog box should be accessible via a button on the login page, although if pressed, but there is already a PID set, it should ask for confirmation before displaying the dialog box.
When the dialog box is OK'd, the user should be registered into the database with "STU" and with a new PID. If the registration is successful, the new PID should be displayed to the user with some information on what to expect next. The PID should be recorded in the configuration and the password also, if the user allows the program to remember it. An automatic login should be performed as well.
From then on, as long as the pilot is in STU status, the Login button on the Login page should bring up a page that displays two buttons: take the entrance exam and fly the check flight. It should also display some general information on where the new pilot can find extra information, etc. One or both of the buttons may be greyed out if the extrance exam and/or the check flight has been performed (and not refused).
The entrance exam button should bring up the appropriate Moodle exam in either the user's browser (preferred) or in the built-in one. An automatic login should be implemented there too.
The check flight button should go to an aircraft type selection page and then load the corresponding built-in flight and start the flight with that. At the end of the flight, the user should be able to send the PIREP as normally, but a different text should be displayed.
If the entrance exam has passed and the check flight PIREP has been accepted too, the user's status should be changed to FO, it should be given the default rights and the type certification for the type the check flight was flown with.