Maybe after this overhaul we should start from v2.0.0 as the 1st tag?
We can do that by creating a "Releases" for the current state.

it would be very nice if one could navigate his previous commands with the "up" and "down" keys, instead of typing again and again.

That's a nice project you've created here!

Unfortunately, from a legal point of view, it's illegal for us to use, modify or redistribute your code, even without a commercial purpose.

I don't think that you intend these restrictions, but this is the common way for all GitHub repositories which do not include a license file.

Therefore, I'd suggest you to add a LICENSE file to this repository. If you want to leave it free to everyone, I'd suggest you the OSI-approved 0-clause BSD License: https://tldrlegal.com/license/bsd-0-clause-license

You can then just add this to your LICENSE file:

Copyright (C) <year(s)> <copyright holder(s)>

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Thanks!

Tested Browsers

MS Edge & G Chrome (both non-beta/nightly and up-to-date)

Steps to reproduce

0. Go to the website, or download the repo and open the root index.html
1. Select all the text within the examples/bounce.js file, and copy
2. Paste it on the "Definitions" box in the website (while removing the prepopulated text)
3. Run demo() command and hit "Enter"
4. The canvas goes blank, and the turtle is nowhere to be found

About the other files

• clock is fine
• randstripe has the same problem as bounce
• sierpinski works as expected
• spiral: same problem

Etc

I'm currently trying to pinpoint the cause of the bug

If a command is executed, and the user uses the command history to re-run the cmd again, the command doesn't execute. I suspect this is because the event listener uses change instead of keydown.

I'll fix this now in #9 PR