I spoke with Ryan this past week about the issue I raised to Dylan about the user classes, and he agreed that it would be smart to split them up.
To Summarize:
When a user starts the application, the player is created as a PlayerObject. This class holds the methods that check for FirstTimePlayed (where the user sets their username if it is the users first time using the application), and similar methods.
However, this class also controls methods and variables for controlling resources. Since the Spectator object should not have these methods, I brought up separating these methods out into a PlayerObject class and having the other methods placed in a UserObject class.
This would allow us to create a Spectator Object class, where all of the spectator methods (controlling camera, path views, etc) could be placed. This would make the project neater and also my life easier, which I am a big fan of.
What I Did:
Reading Vectrosity docs (2hrs)
Started building SpectatorObject class (2hr)
Going through new Tower path management with Ryan (1hr)
Design Doc diagrams (3hrs)
No comments:
Post a Comment