precup / turing-machine-sim Goto Github PK

Kevin:
If you enter a test string which uses characters which are not in the alphabet and then 'run' then 'step' over such a character, it silently fails with " Uncaught TypeError: Cannot read property '0' of undefined gDFASimulator.step @ dfa.js:7 gTape.step @ tape.js:71 gTestMenu.step @ test.js:75 "

There should be some message to the user when the browser is getting the list of saved automatas from the user.

Related to issue #5

From Kevin:

The testing bar at the bottom highlights the character it's going to process next. This is a bit pedantic, but I would expect a highlighted character to be one which is currently being processed (so maybe highlighting an edge? not that this is an important feature), not one which is about to be processed. I think it's a lot clearer to have the cursor being between characters rather than over a particular one.

I'd suggest having two radio buttons or a switch for left and right rather than having to type in "L" or "R". Here are some ideas: http://www.google.com/design/spec/components/switches.html#switches-radio-button

Questions to answer:

• Are there trailing and preceding "☐" characters in the main string?
• What if the tape head ends on a blank space before the beginning of the string?

Kevin

I've at least once gotten an error "whileRunning is not a function" at server.js:40, though I can't seem to reproduce it

From Kevin:

"Force directed layout" gives "Uncaught TypeError: gTopMenu.forcedDirectedLayout is not a function"

Low priority. We could also take out this feature.

Please see video: https://app.box.com/s/s3ny7h6yn8vo7ic7yy7e

Jay, I need an interface for showing the message. Thanks!

There's no way to see the alphabet while working on a problem

When I click '+', I can't find the "☐" very easily.

if the edge doesn't have any characters and the user clicks "update", an error message should appear rather than deleting the edge

From Kevin:

I have no idea what the 'end' button does. It's possible these buttons conceptually map to "start" / "step" / "stop"; if so, those are the more usual names.

I can use all of the buttons except save and load, which freeze the screen when I click. There are no console errors. My guess is that the modal appears somewhere off the screen.

From Kevin

Use Max's example:
https://web.stanford.edu/class/cs103/cgi-bin/restricted/tm.html?saved=asdf

From Kevin:
There is no indication that the machine is not running (eg, if you enter a string, run, then change the string, it looks like it's ready to go [or has already processed some characters], but won't actually do anything until you hit "run"). I would expect hitting 'enter' after entering a string would reset the machine such that hitting 'step' causes it to step through that string from the beginning, starting at the start state.

from Kevin:

There's no indication that the machine you've entered is not a DFA (eg, missing edges)

Kevin:

Actually submitting leaves the button saying "Submitting..." seemingly forever; I can't tell if it actual submits or not (though the console shows an XMLHTTPResponse)

From my own testing: No error message appears in the console. Possibly server side error.

Seems to be an issue on my laptop?

It looks like it might require tspans inside text tags.

Error from console:

TypeError: undefined is not a function (evaluating 'names[i].endsWith ("@stanford.edu")')

I've tested Chrome, and submit functionality works fine. We should test Firefox as well.

Enter nothing, only set initial state, st:

Uncaught TypeError: undefined is not a function
bulk.js:30 (anonymous function)
bulk.js:27 gSimulator.runTests
modal.js:29 gModalMenu.submit
tm.html?type=dfa&charset=yd&pset=0&problem=1&mock=1:237 onclick

Kevin:

If a node was marked as the current node as part of a test, and then you load a saved automata, the little red halo remains where it was.