11 ms·

Sadly the website seems to have fallen over for me. I am really interested in how it works. From what I could see it seems a bit more cumbersome, than my appro

• duncanmeech 12y ago
  agreed, but compiling the code does have the benefit of providing syntax checking and you are assured the full benefits of whatever JS engine your browser is running. How do I create new algorithms on you site? I could not figure that out.
  • wijt 12y ago
    I make use of Tailspin [1], which is a JS-in-JS interpreter and almost fully ES262 compliant. The visualisation gets called on every line of code and updates itself based on inspecting the interpreter state. Two benefits are, the visualisation code is kept completely separate from the code being visualised. And secondly Tailspin offers the ability to step back in time. In terms of creating algorithms, it's a bit of an awkward wiki syntax at the moment, see the tutorial [2] and bubble sort example [3]. [1] http://wthimbleby.github.io/tailspin/ http://wthimbleby.github.io/tailspin/ [2] http://will.thimbleby.net/algorithms/doku.php?id=creating_an_algorithm http://will.thimbleby.net/algorithms/doku.php?id=creating_an... [3] http://will.thimbleby.net/algorithms/doku.php?id=algorithm:bubble_sort http://will.thimbleby.net/algorithms/doku.php?id=algorithm:b...