Gcompris is now able to keep track of the kid sucess and failure. This page describe the formatting used in order to document it and let other project share it.
DATE;HOSTNAME;USERNAME;APPLICATION;ACTIVITY;LEVEL;SUBLEVEL;STATUS;USEDTIME;EXPECTED;GOT
DATE: User locale string date (Human readable)
HOSTNAME: the user pc hostname
USERNAME: can be the system username of an application specific username if implemented
APPLICATION: your application name. gcompris for us.
/ACTIVITY: the name of the activity played
LEVEL: the level
/SUBLEVEL: the sublevel
STATUS: One of PASSED, FAILED
USEDTIME: how many time the kid spent from the start of this activity to the PASS/FAIL event
/EXPECTED: The expected value (a string explaining what was expected)
Or a free string where the application can store any information to help the teacher determine what went wrong
/GOT: A string explaining what the kid answered
(/) Field may be empty
Example for a failed log in french: mar jan 20 00:38:12 CET 2004;bruno.maison;bcoudoin;gcompris;writing;1;2;FAILED;14;hello;helo
This format is implemented in gcompris but is subject to change. These boards are not using gcompris_display_bonus to inform the kid of failure/sucess. Thus we won't get traces on them. The good new is that all the others are ok.
chess.c clickgame.c maze.c memory.c planegame.c submarine.c (need to add a goal as well. Why not a diver to pick up ;) wordsgame.c
Help welcome.
| Page Execution took 11.927 seconds |