[gcompris-devel] Log Module for gcompris

Ralf Jardon ralf.jardon at uni-koeln.de
Tue Jan 20 06:27:01 UTC 2004


Am Di, den 20.01.2004 schrieb stasZ um 10:41:

> Agree, i think that your comma separation is the form we should use.

Yes, that´s my opinion too. The export/import possibilities with CSL are
a great advantage.

> The first thing we should do before anything else is agree on the  
> format of the logs and the description of the fields.

Sounds good...

> My suggestion of the fields:
> applicationname,date,starttime,host,user,level,number of excercise, 
> result,endtime,comment,misc;

OK, but in some boards the children can make different kinds of errors. 

For example in "smallnumbers":

The goal of this board is counting the dots on a cube and typing the
appropriate key on the keyboard. An unexpected source of error here is
to type a letter and not a number. Another possibility is to type the
same wrong number again and again. I such case i need a logging output
that shows me the kind of errors and the frequency of errors.

An example output for smallnumbers can look like this:

date, app-name, host, level, starttime, endtime, usedtime,
detailed_result (e.g. 555tzh76568hijgh9), comment, misc; 

In the example above the detailed result shows the way of finding the
solution (the typed keys), the solution in this task was the "9". That
kind of logging makes the "result" cell redundant.

Another (and IMHO better) way to log all possible errors is writing a
new line each key pressed. For example:

date, app-name, host, starting_session;
date, app-name, level, usedtime, result_key(1), FALSE; 
date, app-name, level, usedtime, result_key(2), FALSE;
date, app-name, level, usedtime, result_key(3), FALSE;
date, app-name, level, usedtime, result_key(4), TRUE;
date, app-name, host, ending_session, comment;

In that case the starttime and endtime are redundant, we have a starting
and ending line. The great  advantage in this kind of logging is to have
the time between the key pressing (the thinking time of the chindren) 
so i would prefer this kind of logging. In fact it is a key-logging :-)

Logging the user name is IMHO not necessary because i suppose in
practice each children will use it´s own Linux-login. The logfile should
be located in /home/CHILD/.gcompris_log or better in 
/home/CHILD/.CHILD_gcompris_log because i have 26 children in the
kindergarten and different logfile-names will make the use simpler.

Bye
Ralf

> 
> Stas Z
> 
> "There are only 10 types of people in this world:
>  Those who understand binary, and those who don't."
>  
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> gcompris-devel mailing list
> gcompris-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gcompris-devel





More information about the Gcompris-devel mailing list