treygilliland / pyscenes Goto Github PK

Add automated testing

Once the project has barebones functionality, add a release

A lot of the code I am consuming to build this project is coming from Pygame_functions by Steve Pagat. As this code is contained under GPLv2, I will need to update my license accordingly.

Currently, PyScenes uses a Game object containing references to classes that manage other parts of the Game. While this is good for separating functionality, it leads to some nasty imports (ex: game.display.background.setBackgroundImage("...")).

This is fine for now, but it may become a messy issue if the dependency trees become too tall.

Where the real issue exists, is that the instance of the Game object used to run the game and the game loop is passed into the scenes that the Game itself is using so the scenes then have access to methods to subvert the way the game loop runs.

To fix this, separate the objects scenes need access to manipulate (such as Mixer, Display, etc.) away from the methods used to run the game so that the scenes can't break themselves.

Add documentation and docstrings to existing code