-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Results / end of experiment usability #238
Comments
We don't have time to do this straight away. It would be nice in the near future though.
I'd say both. For now it's only option 1, and I'm not really excited at adding new features before release at ECCS, but it definitely come in an update. I'm setting this issue as "ECCS optional", but we can continue the conversation. |
Yes, no worries |
:-). Exactly why I love this WebView. Javascript to the rescue! |
A link to an external page indeed sounds great. And yeah, probes continue ! |
Decision time. I suggest:
Problem: if the user wants to restart, questions will probably have evolved since. It would be a pity to lose a potential recurrent user by feeding him the same questions each time he wants to restart. So the button can change to "restart" and it'll reset the experiment (a bit like the "reload parameters" button in test mode). Problem 2: the user then loses all the information from the previous times he did the experiment. For this we need the login mechanism, and the user can browse his past experiments on the website (aaaaargghhh implementation!). |
Login: #324. |
I don't know:
reloading of parameters is a problem per se #325 |
So there was no decision here.
|
I'd say: add a "stop probes" button under the "Days elapsed" once results are available. The button turns into a "restart exp" once clicked. And clicking that does the same as "reload parameters" in test mode (keeps profile, but reloads questions and resets all the rest). |
When the 30 days are over
Show we
@wehlutyk @MklBst
The text was updated successfully, but these errors were encountered: