criswxart / go-tour

Automatically exported from code.google.com/p/go-tour
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Feature request: gotour should remember the content of the edit boxes #179

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. edit a the content of a lesson
2. close gotour by killing the process
3. re-start gotour
4. refresh the browser

Q: What is the expected output? What do you see instead?
A: The edited content should be recovered. Instead, the content is restored to 
whatever it was initially when starting the lesson. This is really frustrating 
when the interpreter hangs, like when having infinite loops in the code due to 
beginner bugs.

Q: What version of the product are you using? On what operating system?
A: gotour 209:dc7aec0e8fcd running on Ubuntu 14.04, x86_64

Please provide any additional information below.

Original issue reported on code.google.com by cristi.m...@gmail.com on 26 Aug 2014 at 11:28

GoogleCodeExporter commented 8 years ago

Original comment by a...@golang.org on 26 Aug 2014 at 11:40

GoogleCodeExporter commented 8 years ago
This issue was closed by revision 380970f2c8c6.

Original comment by campoy@golang.org on 28 Aug 2014 at 5:33

GoogleCodeExporter commented 8 years ago
The fix seems to cover the use case of closing the browser tab and re-opening 
it, but it still doesn't work for when the gotour process is killed and 
restarted, or at least I wasn't able to figure out how to do it.

When gotour is killed and restarted a new tab is opened with the initial state 
of the code.

The previous tab, containing the changed version of the code, is still 
available and the user can certainly copy the code over to the new tab, but 
can't simply reuse it and continue working.

Original comment by cristi.m...@gmail.com on 31 Aug 2014 at 3:11

GoogleCodeExporter commented 8 years ago
Did you reinstall the tour? I just tested it and worked for me.

1. go get -u code.google.com/p/go-tour/gotour
2. gotour
3. modify code in the page
4. kill gotour
5. gotour
6. the modified code appears on the page

Original comment by campoy@golang.org on 31 Aug 2014 at 7:08