<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">Le 19/03/2016 20:33, JAZEIX Johnny a
écrit :<br>
</div>
<blockquote cite="mid:56EDA991.1070701@gmail.com" type="cite">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<div class="moz-cite-prefix">Hi,<br>
<br>
On 03/19/16 14:49, Emmanuel Charruau wrote:<br>
</div>
<blockquote
cite="mid:CA+jbWcF6NdNksHm9H-vRnj0Au3bzcpqh+vB3+e2wbrDCVcSadg@mail.gmail.com"
type="cite">
<div dir="ltr">Hi,
<div><br>
</div>
<div>If we go this way, and since we are reworking the
architecture, could we not implement a third level depth?<br>
</div>
<div>Let me give you an example.</div>
<div>We want to provide more specialised vocable classes for
the lang activity (the one to learn vocable).</div>
<div>We could have the following tree</div>
<div>vocable</div>
<div> - kids 5-6</div>
<div> - kids 7-9</div>
<div> - etc</div>
<div>but also</div>
<div><br>
</div>
<div> - nature</div>
<div> - geography</div>
<div><br>
</div>
<div>etc.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>What do you think?</div>
<div><br>
</div>
</div>
</blockquote>
</blockquote>
<br>
Hi,<br>
<br>
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.<br>
<blockquote cite="mid:56EDA991.1070701@gmail.com" type="cite"> <br>
<blockquote
cite="mid:CA+jbWcF6NdNksHm9H-vRnj0Au3bzcpqh+vB3+e2wbrDCVcSadg@mail.gmail.com"
type="cite">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> If we can do this
we and this gives good results we can go further to
include more requirements like:<br>
<br>
- Inter Activity dependencies<br>
</div>
</blockquote>
</div>
</div>
</blockquote>
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...).<br>
</blockquote>
<br>
You are true, this is needed, we can't really make it works without
this feature.<br>
<blockquote cite="mid:56EDA991.1070701@gmail.com" type="cite"> <br>
<blockquote
cite="mid:CA+jbWcF6NdNksHm9H-vRnj0Au3bzcpqh+vB3+e2wbrDCVcSadg@mail.gmail.com"
type="cite">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> - Core API level
(versioning of activities versus the core)<br>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
It will be needed anyway because if we have some issues with one
activity, it will be nice to know which version :).<br>
</blockquote>
<br>
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.<br>
<br>
Bruno.<br>
</body>
</html>