[gcompris-devel] Log Module for gcompris

[Olivier Samyn]

Hello Bruno,

I began,  yesterday, to check and update the python wrapper and his docs...
So I will add those new functions in it :)

For xml output and so on, why not to use an external program that will 
interpret the whole raw log file and generate something more readable ? 
just like what is done with for example apache logs ?

A last question: how do you create the ChangeLog file ? manually edited ?

Olivier Samyn.

Bruno Coudoin wrote:

>I just commited the first implementation of the traces in gcompris.
>The log is written to a file named .gcompris.log in the home directory.
>
>The API is:
>
>Only gcompris_log_set_reason is generaly needed for boards. In fact,
>start and end are managed by gcompris core. For the end, it relies on
>the bonus API so the boards that do not use it 
>
>/* gcompris internal only */
>void gcompris_log_start (GcomprisBoard *gcomprisBoard); 
>
>/* Use it to tell the teacher where the kid failed */
>void gcompris_log_set_reason (GcomprisBoard *gcomprisBoard, gchar
>*comment); 
>
>/* Do not use it if you use the bonus API in your board */
>void gcompris_log_end (GcomprisBoard *gcomprisBoard, gchar *status);
>
>  
>
>Here is an example of a failed log in reading
>mar jan 20 00:38:12 CET
>2004,bruno.maison,bcoudoin,readingv,1,1,FAILED,14.000000,The word to
>find was 'vit'
>
>
>Ralf, it's already better I think than your implementation (thanks for
>your help, I took part of your code ;).
>
>Stasz, on your side, what do you think of it. Is this ok for childsplay
>or we need something else.
>I though we could at the application name in the format so that if we
>want to have a share single trace file on a host, it would work.
>
>Next, I will look at a simple trace viewer. Basically, I think of a
>table in which you can filter. It should be enough for a teacher to find
>it's kids results. A button will let him reset the log when think
>becomes too old and huge.
>
>I don't plan to work on XML, OO.org or remote sharing of this trace for
>now. Let's go step by step and see if we really meet our users with this
>feature.
>  
>