H. G. Muller wrote on Tue, Jan 22, 2019 06:13 PM UTC:
It seems that IE is not able to run Jocly, then. I just finished adding code to it to keep track of the players' time usage, but currently the clocks are always initialized to 10 days per player. Pretty far from blitz, I suppose... It was really designed as a turn-based server for correspondence chess (variants).
Of course everything would still work if you initialize the user clocks to a very short time, but the way the interface works would be pretty cumbersome: When your opponent moves you would not automatically get to see it. In stead you would have to keep loading the game by clicking it in the game overview until you see that it is your move again. The idea was that you would typically not sit at the keyboard anyway when your opponent moved, and that the computer might even be switched off. And after you made the move on the display, you would still have to press a 'submit' button before it gets sent, to give you the opportunity to verify it for mouse slips and the like. All that of course takes very significant time compared to a blitz game, slowing you down by perhaps a factor 5.
Of course this can all be fixed; I could of course add an option that would sent the played move automatically, which the user could tick when he considers speed of more importance than reliability. And I could have the web applet keep downloading the selected game automatically for as long as the opponent is still on move, every second or every 10 sec. (The frequency depending on how much time is still left on the clock; if it is days, checking every 10 minutes would probably be fast enough.)
It seems that IE is not able to run Jocly, then. I just finished adding code to it to keep track of the players' time usage, but currently the clocks are always initialized to 10 days per player. Pretty far from blitz, I suppose... It was really designed as a turn-based server for correspondence chess (variants).
Of course everything would still work if you initialize the user clocks to a very short time, but the way the interface works would be pretty cumbersome: When your opponent moves you would not automatically get to see it. In stead you would have to keep loading the game by clicking it in the game overview until you see that it is your move again. The idea was that you would typically not sit at the keyboard anyway when your opponent moved, and that the computer might even be switched off. And after you made the move on the display, you would still have to press a 'submit' button before it gets sent, to give you the opportunity to verify it for mouse slips and the like. All that of course takes very significant time compared to a blitz game, slowing you down by perhaps a factor 5.
Of course this can all be fixed; I could of course add an option that would sent the played move automatically, which the user could tick when he considers speed of more importance than reliability. And I could have the web applet keep downloading the selected game automatically for as long as the opponent is still on move, every second or every 10 sec. (The frequency depending on how much time is still left on the clock; if it is days, checking every 10 minutes would probably be fast enough.)