motoko-tutorial/introduction - Thoughts on making extended Lesson work a little friendlier.

[GeorgeKoller]

I am fully appreciating these Interactive Lessons, and spending considerable time expanding on the base limits to experiment with such of them, for example using instead of as the basic object be appended to a Buffer, List, and so on.

(It's truly a privilege, and a joy for me to have a responsive interpreter to do this in! On the other hand (re-bruidling, and re-deploying canisters using the CLI on small changes is just painful. So I'm not being critical.

My first suggestion is that there could be a Button added inside the interpreter window to "Previous Lesson" - going back one lesson now requires going back to beginning and going forward. Not a big thing.

Is there any chance of making our work persistent? Or perhaps allowing the lesson program file to be saved, and re-loaded?

A problem I have had several times is that while I'm expanding a lesson and hitting the "Run" button again and again, I
will hit "Next" button by mistake, and lose everything, and can't even go back without restarting and stepping though again.

If file Save/Load were available, then an "auto save" on Next would accomplish the above neatly.

[romario333]

Hello there,

thanks for the feedback!

Making the work persistent via auto-save is a good idea and I'll add it to our backlog.

As to navigating to previous lesson, there is already button for that:

[GeorgeKoller]

Roman, Pleased and impressed to get this response so quickly. Yes, you are right, after I thought about it I recognized that Random access certainly includes "Previous". Note, that I have been really enjoying using the interpreter, and wanted to systematically expand on some of the lessons to explore step by step. It would be nice to be able to come back and expand in steps. So being able to save EACH lesson as a file (automatically named to the lesson#?) would be most helpful. If during sessions a buffer/file could be *automatically saved for each lesson, * this would be excellent, and I expect it would encourage exploration and expanding on the lessons. However, just automatically saving the program code from the Last Lesson before exiting would be a basic, very helpful first step imho, and would complicate, or slow someone only reviewing. Hope this helps, George Am Mi., 27. Dez. 2023 um 01:31 Uhr schrieb Roman Masek < ***@***.***>:

…

Hello there, thanks for the feedback! Making the work persistent via auto-save is a good idea and I'll add it to our backlog. As to navigating to previous lesson, there is already button for that: ***@***.*** (view on web) <https://github.com/agorapp-dao/agorapp-feedback/assets/373775/95065a90-9a7c-4c94-91e4-9584b8c93309> — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BDEEGXUIJIQUAFFJY7DHGFDYLPFEBAVCNFSM6AAAAABBA7UDJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZQGAZDQNZZHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>