Since Pyweek is over, this project is getting renamed to DBCM, so update your watched tags accordingly.
Today's effort was setting the framework for animating battle scenes. Since, ya know, it's a little boring without it. This meant setting up the battle frame from the menu screen, and start puzzling how to animate over time. The solution is of course setting a bunch of variables in the model that are "future" or something similar and setting the animation equation to move from current state to future state over time. Then of course when the animation is done and the animation is over, the model needs to commit the change to the actual values. No big deal, right?
So, the second issue is how to handle time. To date, I've been using Pygame's Clock module to handle it, but it's hooked directly to the model and it's the only pygame call in the model at the moment. So, the plan now is to cut that out and make that a new controller that I can manipulate in its own time. Of course, a second controller means either hooking in each one separately, or making a mediator for the controllers to listen to that handles subscription to the main mediator.
A quick branch and hour of puzzling later, and that's what's happening behind the scenes now. The game itself doesn't look any different. Yet.