Return to repo list


Tactical RPG written in python, using pygame.
Return to

commit caea4fd44304546ecb051af0c95447da85c3af83
parent 3f597203e9da656e28c50690893ca2843760b426
Author: Erik Letson <>
Date:   Tue,  2 Feb 2021 17:27:55 -0600

note to self on further UI implementation

Msrc/ | 7+++++++
1 file changed, 7 insertions(+), 0 deletions(-)

diff --git a/src/ b/src/ @@ -11,6 +11,13 @@ from .constants import * # represent a complete refresh of the status of the turns; 2) it is used by itself in kill_piece and possibly in other places. The # project_turn_order method is one of a few that should probably not be used by itself, but rather only in the context of refreshing the # TurnManager's turn state. This hints at possible expansion of what 'refreshing the turn state' even means in the future. +# 2. The UI elements that TurnManager handles could possibly be handled instead by MenuManager and defined in a JSON as a menu object. This would +# require a major overhaul of the TurnManager object to decouple the UI functionality (which would also greatly affect the ManagerBus and +# Interface objects), as well as an expansion of the Menu object to be able to handle what the turn UI does with its generalized functions. +# This would be a long-term goal and probably part of a wider refactor targeting TurnManager and BoardManager particularly, but it should +# serve as a warning to implement further UIs through MenuManager. Ideally, Menus and Scenes would be general enough that they could, between +# themselves, represent the majority of the interactive (and non-interactive) gameplay, leading to the game mostly being just a series of +# complex JSON files. # This file contains the following: # 1. The TurnManager class, which handles turn order and displaying turn info in the GUI