|
|
19aa959c64
|
Try and make sense of the two data structures related to games with a good renaming
|
2020-01-23 22:17:57 +01:00 |
|
|
|
428e48f6f4
|
Follow move of 'logs' into PublicGame structure and start implementing re-sync protocol on the client side
|
2020-01-20 22:58:57 +01:00 |
|
|
|
ef947f7942
|
Keep previous state of game and use it to replay latest move
|
2020-01-18 23:10:22 +01:00 |
|
|
|
97b0bc0cc8
|
Follow «Coordinates» change in protocol
|
2020-01-18 09:35:51 +01:00 |
|
|
|
8cfcd419ef
|
Store all of game message, to get the log, why drop it and have to generate a fake message ?
|
2020-01-15 18:10:52 +01:00 |
|
|
|
2563a44c11
|
Start importing Game Screen module, everything is broken due to class prototype definitions, also start cutting this gigantic module into small ones
|
2020-01-15 18:10:02 +01:00 |
|
|
|
b8c95646dc
|
Factorize game proposals insertion to avoid spreading use of opponent and timestamp
|
2020-01-15 18:09:50 +01:00 |
|
|
|
173d71472e
|
Implement persistence and retrieval of Game states and entries
|
2020-01-15 18:09:48 +01:00 |
|
|
|
d308d35069
|
Remove 'itemMaker' parameter to Table instanciator since it all amounts to copying all the object passed
|
2020-01-15 18:09:48 +01:00 |
|
|
|
26020a5539
|
Keep sorting things between view, models, full game states and games list entries — should yield to simplifying Table module
|
2020-01-15 18:09:45 +01:00 |
|
|
|
abba380f3f
|
WIP: still trying to figure things out between Games models, views and the part persisted in localStorage
|
2020-01-13 08:39:32 +01:00 |
|
