[GCompris-devel] Introduction + GCompris Idea Discussion

[Bruno Coudoin]

Le 19/03/2016 20:33, JAZEIX Johnny a écrit :
> Hi,
>
> On 03/19/16 14:49, Emmanuel Charruau wrote:
>> Hi,
>>
>> If we go this way, and since we are reworking the architecture, could
>> we not implement a third level depth?
>> Let me give you an example.
>> We want to provide more specialised vocable classes for the lang
>> activity (the one to learn vocable).
>> We could have the following tree
>> vocable
>>   - kids 5-6
>>   - kids 7-9
>>   - etc
>> but also
>>
>>   - nature
>>   - geography
>>
>> etc.
>>
>> User would be able to first select the lang activity, then in lang
>> activity select for example "kids 5-9" and "nature" but not geography
>> as he does not want to download these classes.
>>
>> What do you think?
>>

Hi,

I understand this need but I would prefer to leave this out at this
stage. I am afraid it starts to be complex enough, if we try to do
everything in one go we risk doing nothing and make no progress. Let's
make baby steps.
>
>>     If we can do this we and this gives good results we can go
>>     further to include more requirements like:
>>
>>     - Inter Activity dependencies
>>
> Won't it be needed? I mean, if user want to download an extended
> activity (erase_2clic, chronos...), he will need the activities they
> are based on (erase, babymatch...).

You are true, this is needed, we can't really make it works without this
feature.
>
>>     - Core API level (versioning of activities versus the core)
>>
>
> It will be needed anyway because if we have some issues with one
> activity, it will be nice to know which version :).

My point here was to download only activities that are compatible with
the version of the core that the user has. But we that also means doing
versioning at activity level.

Bruno.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/gcompris-devel/attachments/20160319/e523ba8c/attachment.html>