Magic Cube

Major abstraction - automatically compute the 'computeRowFromOffset()' function from CUTS.
Still one thing left: it appears like the CUTS of Mega/Kilominxes are not correct.

Move the Movement class from ObjectList to individual object classes.

Move actual solving the object to PreRender.

(before we had a 'solveObejct()' in preRender already, but that one just starts the Solve Effect!)

Fix the problem reported by Samsung -

1. Fire off the app
2. minimize it, select 'Multi window'
3. put some other app in the lower half of the screen
4. close the lower app
5. our app used to fail to display the upper and lower menu bars.

TwistyObject's ObejctScreenRatio and InitScreenRatio shouldn't be static. Make them non-static.
Otherwise, if the current object is, say, a cube (initSR=0.5), we fire up tutorials and start a tutorial for something with vastly different ObjectScreenRatio (Jing- initSR=1.64), then come back to the Main Activity - so there's a cube on the screen again - the ratios stay at their Jing values, which screws up detection of rotations.

Improve debugging in BlockController.

add possible scrolling to the 'object' popup in case the grid of objects does not fit on the screen.

Progress with RubikControl.

Lots of changes :)

Progress with RubikControl.