objectives display

[Emmanuel Charruau]

Hi,
I don't see so far any activity where you should not give the objective
when presenting a new level.
We can obviously do a logic test and not trying to display if there are no
objective given.
But it is important to tell either the kid or its parent what is achieved
for a given level.

Emmanuel

Le ven. 2 août 2019 à 18:28, Johnny Jazeix <jazeix at gmail.com> a écrit :

> Le ven. 2 août 2019 à 15:07, Timothée Giet <animtim at gmail.com> a écrit :
> >
> > Le 02/08/2019 à 14:30, Emmanuel Charruau a écrit :
> > > Hi Akshay,
> > > I tested multipledata on smallnumber and smallnumber2 and I am
> > > wondering if we should not change the way objectives are recalled.
> > > At the moment to hide the objective you tap on the objectives area,
> great.
> > > But to get it back you have to tap on the same area, and there is no
> > > way for the user to know what this area is.
> > > I think you should change the way it reappears and show it back
> > > whenever the screen is tapped (outside the other buttons obviously).
> > > Mentors, what do you think?
> > >
> > > Regards,
> > > Emmanuel
> >
> > I think we should both hide and show the objective when clicking
> > anywhere on the activity area (of course excluding the bar buttons and
> > the virtual keyboard area).
> >
> > Timo.
> >
> >
>
> Do we want the same behaviour for all activities or only for specific
> ones? The question behind is: do we try to do something generic (might
> be tricky but would avoid a lot of code duplication) or do we do it
> specifically for some activities?
>
> Johnny
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/gcompris-devel/attachments/20190802/fa5c09c2/attachment.html>