[GCompris-devel] saving the progress for Lang activity.
Emmanuel Charruau
echarruau at gmail.com
Mon Jul 6 21:23:22 UTC 2015
Hi Guys,
Something which would be great to have in the activity progress generic
solution is an history.
Pupils learn a lot from their own mistakes, and they love to see what was
going wrong in their answer... if we give them a chance to correct it.
(opposite of french system where after an exam you don't come back on what
you failed)
So we need to have a trace somehow to make them think about what they did.
Anglaisfacile shows a good example of what we could show
http://www.anglaisfacile.com/cgi2/myexam/voir2r.php?id=26838
I know history is difficult to maintain but I think it is worth it.
What do you think about it?
Allon
2015-06-27 22:20 GMT+02:00 JAZEIX Johnny <jazeix at gmail.com>:
> Hi,
>
> to be more precise, the point here is to see how we can have a generic
> solution to provide activity progress and status to users (either teachers,
> parents or even children).
>
> The proposed solution is to use a new config file containing only the
> statistics for all the activities.
> Then, it should be easy to create views for teachers and users. I don't
> think saving it in a qml is interesting (you probably misunderstood why I
> was talking about qml, it's for the translations not for saving stats).
> A simple .ini file like for configuration could be enough. Then, we need
> to think if there is an interest to use a database instead (maybe easier
> for integration with the admin interface? We can even think of having an
> activity showing the progress :))?
>
> For the coding part, we should probably have a qml element doing all the
> job and use it in the activities (maybe in the ActivityBase so
> loading/saving can be handled there).
>
> On 06/27/15 15:04, Siddhesh Suthar wrote:
>
> hello,
>
> I am porting language learning activities. Its almost complete. Now i
> have to save the progress of words which a user has learnt per lesson wise.
>
> The current idea I discussed with JohnnyJ is to save the progress in a
> qml file inside (resource/data) of the activity. then, we need to see how
> to define the format.
> There can be different approaches to it.
>
> 1. we store only the savedProgress corresponding to its lesson, and
> everything else for the menuModel will be fetched from words.json through
> lang_api
>
> To precise a little, savedProgress is a js variable storing while
> playing the activity the percent of completed words for the current word
> category. It is not yet permanent so every time the user restarts GCompris,
> the progress is reinitialized.
>
>
> 1. we also have to think if we can make this saving generic and where
> do we store it (as I don't think it is great to save it in configuration
> file because then as we want this to be potentially usable by other
> activities, putting these in the config file don't look like to be a good
> idea).
> 2. johnny jazeix added: I would prefer a special file for all the
> progresses because then, if the teacher wants to retrieve all the stats for
> a child, only one file with only necessary data would be better instead of
> all the config file.
> 3. In json, we can't translate (use qsTr()) but you can in qml, so it
> was more to provide the translators all the strings in the same translation
> file they already use.
>
> The last point is not useful for the current issue ;).
>
> Johnny
>
> I would love to hear your ideas about it. Want to know what can be the
> best approach for it.
>
> Siddhesh suthar
>
>
>
> _______________________________________________
> GCompris-devel mailing listGCompris-devel at kde.orghttps://mail.kde.org/mailman/listinfo/gcompris-devel
>
>
>
> _______________________________________________
> GCompris-devel mailing list
> GCompris-devel at kde.org
> https://mail.kde.org/mailman/listinfo/gcompris-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/gcompris-devel/attachments/20150706/db26a550/attachment.html>
More information about the GCompris-devel
mailing list