Open GoogleCodeExporter opened 9 years ago
Original comment by mrlhwlib...@gmail.com
on 18 Mar 2012 at 6:18
Original comment by mrlhwlib...@gmail.com
on 18 Mar 2012 at 6:22
Yes, the popup "Goal Reached" would provide some encouragement. Another
possibility is editing the Study mode line "New: #, Rev: #, ID: #", adding
another bit of information, such as "studied today". Then different users
could set their own session goals, and see how many card they have studied.
The new line might look like this:
New: #, Rev: #, ID: #, Today: #
Or perhaps "ID" should remain last in the list, since it applies only to the
currently visible card, not the whole deck. So:
Today: #, New: #, Rev: #, ID: #
Original comment by caviness...@gmail.com
on 23 Jun 2013 at 3:34
I like the idea for displaying the information in the info bar. Personally I
don't like the popup or nag people they have reached goal. I don't want to
prevent people leanring more. But I just provide information for the user to
control their learning speed. Also I can even display the negative number if
they exceed the goal.
One quesiont is that should the goal static or dynamic. I.e :
Static: You set 100 cards /day. Then it is always 100/day.
Dynamic: There are 1000 new cards. If you can to learn in 10 days, the goal is
100/day. But If on day 2 you learned 550 cards, the day 3's goal is 50 / day.
Original comment by mrlhwlib...@gmail.com
on 25 Jun 2013 at 3:31
I do like the idea of adding the information to the info bar, so those who want
to use it can, those who don't aren't being nagged. But I have no strong
preference whether it is a count-up or a count-down counter.
A count-up counter could be used be everyone, just keeping in mind the
individual goal.
A count-down counter, if used, should allow the user to adjust the (static)
goal. I don't see the need for a dynamic goal. If I fail to reach the goal
one day, I'll try to do more the next. If I know I made greatly passed the
goal today, I may not try quite so hard to reach it tomorrow.
Original comment by caviness...@gmail.com
on 26 Jun 2013 at 8:16
Original issue reported on code.google.com by
mrlhwlib...@gmail.com
on 18 Mar 2012 at 6:18