Improve the logging of the framework to allow different levels of logging and logging to files.
NOTES FROM MEETING:
What logging do we want:
1. Development and debugging (with levels)
2. "Transcripts" of pilot tests for usability research
3. Audit trails for production usage, outlining each change and each transaction with the system
a) including call origins/destinations for network or workload analysis at runtime That sometimes gets forgotten
Potential 3rd party libraries:
Select 3rd party library (Steve Lee and Yura)
add manual log lines at strategic places to give developers and users a high level view of system behaviour. E.g. what component has run, perhaps what function, and important data at clear points.
E.g.: matchmaker has started, matchmaker has finished, settingshandler has run
Make sure logged preferences are in the same format as the preference sets to allow easy copy & paste. e.g. reproduce a scenario where the matchmakers did something stupid