Issues/feedback related to v0.3

[gubloon]

Issues and feedback related v0.3

Tasks

Beta Give feedback

1. Readability of "Help" section needs to be improved
2. Behaviour of the "Instructions" section is inapproriate - it simply toggles between appearing and disappearing when "instructions" is clicked. And also it replaces the output section which loses results of the last run.
3. Implement links for each example, in a way they can be shared individually
4. Advice provider example runs into failures
5. Std library example runs into failures
6. Behaviour of "proving" toast component when tried to prove on a failing code needs to be fixed
7. The button to download the ".masm" files is counterintuitive - it is hardly recognizable as a download button
8. According to its behaviour the collapse button in the input panel is supposed to change from "+" to "-" rather than changing its colour from green to grey.
9. Proving should run on a worker thread #174
   UX playground +2
10. The debug view has few areas where it can be fixed/improved: the relevance of green numbers at the initial stage is very less, the "|<" and "<<" buttons does not appear to work when pressed first - shall be disabled in that case,
11. It's hard to understand what is the VM's stack when going backwards; esp. if the state is changed to use a table.
12. Using the buttons ">>" and ">|" seem to print only the last state of the VM. That is not super useful for debugging one wants to see all intermediary values.
13. Verification of the matrix multiplication doesn't work
14. There is no output shown when "Prove" button is clicked

[Dominik1999]

Behaviour of the "Instructions" section is inappropriate

Can you elaborate on this?

[Dominik1999]

"Proving" appears to blocks the browser as it runs in the render thread. Ideally proving should run on a worker thread.

I think for this point we need a different issue and maybe this can be done by our contractor even?

[gubloon]

Behaviour of the "Instructions" section is inappropriate

Can you elaborate on this?

Behaviour of the "Instructions" section is inappropriate - it simply toggles between appearing and disappearing when "instructions" is clicked. And also it replaces the output section which loses results of the last run.

Maybe we need to think of a better way of handling the instruction section - right now, it just appears to interfering a program's flow of run/debug/prove/verify.
Since it's going to be a direct reference for the code, it may not be a good idea to handle it in a separate page like how "Help" is done .
Either we can reduce size of the "instruction section" so that it always sits along with the output/program info box on the right side or we can embed a CLI in the playground which can provide information(instructions being one of them) or a way of interfacing with the VM and rollup - sounds a bit advanced but I had this idea in the initial mockup.

[gubloon]

"Proving" appears to blocks the browser as it runs in the render thread. Ideally proving should run on a worker thread.

I think for this point we need a different issue and maybe this can be done by our contractor even?

Maybe we can consider that too; they could have put more thought in their approach here so that it's structured well on the background. It is not entirely about the frontend/can be fixed just on the surface.