After finishing implementing the game sequence, there are still some boring points to do, like saving and presenting the highest score.
To understand, I have to explain the logic of my framework : a Game is a collection of Gamelets that are independants. For instance, I have a gamelet for the main menu, one for the actual game, etc... And now I have a gamelet for the player stats.
How do these gamelets exchange data ? I use a Session object (a simple maps of Objects identified by a String), like a web application. So my gamelet for the game save the player stats in session if they are better than the last data previously saved.
More, I also have to take care to save those data, and retrieve them when restarting the game.
All of that is booooring, and I delayed this work for nearly a week.
The good thing is that the delay was used to create some code template for eclipse to speed up code writing for my next game, including those data stat management. So I did not entirely loose my time.
Another good thing is that I came up with the idea to promote my other game on this screen too. So now I'm busy coding this screen, and I hope to finish this week.
But the bad thing is that I have to reschedule again, and there will be more change than previously done, in the hope to deliver my two versions of the game by the end of November.
On a side notes, I'm starting to think about some post-mortem analysis, and it becomes clear to me that :
- each gamelets should require at least 2 weeks to be done.
- I have underestimated the reusability of the code of my previous code, mainly because I could not help but rewrite code to get better quality code (to my mind), instead of only copy/paste/patch existing code. I don't regret that, because I prefer code quality to deadlines, and I have the luxury to abide to this preference because it is a personnal project. But the consequence is rescheduling, and I have to take care of that next time.