mtyka / grooviks-cube Goto Github PK

We need to have logs in the cube server for anomalous events such as 
communication failures with the arduinos.

In addition to a range of difficulty options, allow the client to choose to 
play the cube as it currently is, rather than scrambling.

currently we reconnect to disconnected lightboards very slowly (30s?).  We 
should make it MUCH faster, and also only attempt reconnecting if we have less 
than 11 lightboards are connected

When the cube is in game state SINGLE, if a second (or third) player selects a 
single player mode, that player should be queued on the server to take control 
of the cube upon quit (or solve) by the first player.

Open cube_multimode in browser (used FF 6 on OS X 10.6, 15inch).  Last 
characters of message ("e!", "le") appear on left side of screen.

Sometimes fixing a pixel fails, if the pixels being swapped are both being 
swapped into the correct positions.

What steps will reproduce the problem?
1.
2.
3.

Code reference:

http://code.google.com/p/grooviks-cube/source/browse/webserver/templates/admin_c
ube.html

Problem description:

Added JQuery sliders, and changed references to local (instead of Internet) 
resources; one of these changes completely breaks the Admin API

What steps will reproduce the problem?
1. Turn cube on
2. Wait (mttf 10min)

We believe that changing the baud rate on the serial connection may fix the 
problem.

What steps will reproduce the problem?

Open cube_multimode.html with no position and then pressing level difficulty 
buttons reproduces this problem.

Need to have some mechanism for switching the cube into and out of 
single-player mode.

Provide an administration interface for routine tasks:

1) change volume level
2) reboot server & arduinos

1. Start a single player game at position 1
2. Start a single player game at position 2 (goes to wait screen)
3. Rotation controls disappear from position 1

the clients should be able to communicate to each other when any one of them 
wishes to play a three player mode, and when all clients say they want to play 
3 player, 3 player mode should start.  when any one of them wants to stop, the 
mode should cancel out.

The cube server needs to detect when a client has been inactive for too long 
and do a 'quit' transition for that client.