| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
fixed the argument of the call of the wait function used in the reset function (core.js)
|
|
|
|
prolog states
|
|
navigation-bar state and getting back.
Now every state carries with itself the publicly exposed jqScreen object and isModal boolean information, which is used by the globalStateMachine in the actualTransition method.
|
|
|
|
|
|
|
|
|
|
Remove the Language element from the navbar and have "CodeQ" (logo TBD)
send user to the language-selection page.
|
|
So we can resynchronize if something goes wrong.
|
|
New generic actions:
open(time), close plan hint(feedback), test(feedback)
New Prolog actions:
prolog_solve(query), prolog_next, prolog_end
New Python actions:
python_run(program), python_stop, python_input(text)
New robot actions:
robot_run(program), robot_stop(program)
|
|
|
|
|
|
There were three identical copies for {prolog,python,robot}.js.
|
|
entering and leaving the problem solving screen.
|
|
|
|
|
|
|
|
|
|
|
|
decide whether to activate or not the button.
|
|
|
|
|
|
|
|
Hints are not yet covered.
|
|
|
|
|
|
|
|
of the bar), renamed stateMachine to navigation
|
|
|
|
"lines" variable.
|
|
for the top-level block #screen_prolog, made a copy of the latter into #screen_python so the two screens can now diverge.
|
|
|
|
|
|
|
|
|
|
user makes a deletion, and it needs to be recorded in activity.
|
|
|
|
|
|
changed when transitioning
|
|
|
|
|
