Is it acceptable to design my GLSurfaceView as a main control class?
- by Omega
I'm trying to structure a game I'm making in Android so that I have a sound, flexible design.
Right now I'm looking at where I can tie my games rules engine and graphics engine together and what should be in between them.
At a glance, I've been eying my implementation of GLSurfaceView, where various screen events are captured. My rationale would be to create an instance of my game engine and graphics engine here and receive events and state changes to trigger updates of either where applicable.
Further to this, in the future, the GLSurfaceView implementation could also store stubs for players during a network game and implementations of computer opponents and dispatch them appropriately.
Does this seem like a sensible design? Are there any kinds of improvements I can make?
Thanks for any input!