Closed GoogleCodeExporter closed 8 years ago
We did not want to change the turtle app while the contest was going on, so we
intentionally checked in the code without pushing it. The turtle tutorial code
is still very much in flux, so I'd recommend against pushing it now, although
it's of course Neil's call. Another option would be putting the tutorial in
the mooc branch.
If it would be helpful, we could try to put details like intentionally not
pushing code into CL descriptions in the future.
Original comment by sper...@google.com
on 3 Apr 2013 at 5:18
And we've temporarily commented out the tutorial in the codebase so we can push
maze updates, though the tutorials will be reappearing very soon.
Original comment by neil.fra...@gmail.com
on 7 Apr 2013 at 6:53
Hey,
Thank you for the information.
Another question: Is it planned to provide the formely 10th level of the maze?
Maybe separarated? This level is very good to show occurring challenges
whenever something (e.g. a robot) has to navigate through the world or a maze.
Maybe just an 11th level or an additional link, etc.
Best regards
Marc Wollenweber
Original comment by borntob...@googlemail.com
on 7 Apr 2013 at 9:47
User testing of the Maze on early programmers revealed that level 10 was
poisonous in that it forced failure and left a bad impression. It is
definitely not returning to the Maze tutorials.
However, I do think it would make a good stand-alone app. All the code is
still in the repository (r731). Upgrading the random generator would be
needed, since the existing algorithm was weak. Another approach would be to
allow the user to write two code snippets, one that creates a maze, the other
which solves it.
We don't currently have the time to take this on, but we'd be happy if someone
would like to own it.
Original comment by neil.fra...@gmail.com
on 7 Apr 2013 at 5:00
Hey,
I like the idea to have a separate stand-alone app. You even do not have to
change anything, the old version was for our cases sufficient enough. It is
just used (or can be used) to let the users try something and inform them about
problems, e.g. that a righthanded wallfollower or similar are not always
working.
So like you already said, using it in a tutorial would lead to "frustrations"
and lefts a bad impression, but in a supervised environment or as the homework
after getting information about maze problems it would be very benefitial.
Especially because a random (even if you think the generator is weak) maze can
be generated to verify that the solution is not only working for one specific
maze.
p.s. I do not get the last sentence, but this is maybe not a big deal. I hope
this doesn't change the sense of the previously said statements.
best regards
Marc Wollenweber
Original comment by borntob...@googlemail.com
on 9 Apr 2013 at 12:14
Dear all,
I offered a little time to preserve the nice random maze and random position
level. See the attached file.
Comments:
* I modified the maze, which is present in revision r729. Unfortunately, that
means that the new feature to resize the maze is not present. Once again
unfortunately i do not have the time to adapt my version to the newer revision.
* I just made minor changes, so that it is the original maze, but without the
levels and if-else clauses dealing with them.
* Furthermore, I tested it on our server and it seems to run properly, except
of one thing. The storage.js can not be found. When i change
<script type="text/javascript" src="/storage.js"></script>
to
<script type="text/javascript" src="../../appengine/storage.js"></script>
everything works properly
I want to emphasize that this is just a quick modification and that I'm well
aware that the possibility is high that the code will never be used (which is
perfectly ok for me). I just want to give you the option to use it with the
hope that it might increase the development of a stand-alone app.
Original comment by borntob...@googlemail.com
on 12 Apr 2013 at 11:18
Attachments:
Original issue reported on code.google.com by
borntob...@googlemail.com
on 3 Apr 2013 at 5:04