Progress

Rewritten-docs.md

@@ -615,7 +615,9 @@ The very first idea would be to provide progress state based on done messages fr
 
 That is why another solution of progress state was considered. As we know right now one of the best ways how to ensure generality is to have jobs with single-purpose tasks. These tasks can be anything, some internal operation or execution of external and sandboxed program. Based on this there is one very simple solution how to provide general progress state which should be independent on task types. We know that job has some number of tasks which has to be executed so we can send state info after execution of every task. And that is how we get percentual completion of an execution. Yes, it is kind of boring and standard way but on top of that there can be built something else and more appealing to users.
 
-So displaying progress to users can be done numerous ways. We have percentual completion which is of course begging for simple solution which is displaying user only the percentage. ... todo done this
+So displaying progress to users can be done numerous ways. We have percentual completion which is of course begging for simple solution which is displaying only the percentage or some kind of standard graphical progress bar. But that is too mainstream lets try something else. Very good idea is to have some kind of puzzled image or images which will be composed together according to progress. Nice way but kind of challenging if we do not have designer around. Another original solution is to have database of random kind-of-funny statements which will be displayed every time task is completed. It is easy enough for implementation and even for making up these messages and it is quite new and original. That is why this last solution was chosen for displaying progress state.
+
+### Results of evaluation
 
 @todo: how to display generally all outputs of executed programs to user (supervisor, student), what students can or cannot see and why
 
@@ -625,6 +627,8 @@ So displaying progress to users can be done numerous ways. We have percentual co
 
 @todo: discuss several ways how points can be assigned to solution, propose basic systems but also general systems which can use outputs from judges or other executed programs, there is need for variables or other concept, explain why
 
+### Persistence
+
 @todo: where is kept the state (MariaDB)
 
 @todo: and many many more general concepts which can be discussed and solved... please append more of them if something comes to your mind... thanks