jdowner / voxel Goto Github PK

I want the App class to be a fairly generic controller that provides an interface to the renderer. So functions such as loading vertices should be handled by other classes, which may be extensions of the App class. These extensions should be examples that go in the examples directory.

Add text to the readme file explaining (1) what the goals of this project are and (2) how the code is structure and intended to be used.

Create a shaders directory and move the basic shaders there. This is mostly about ensuring that shader loading is explicit about where shaders are being loaded from (rather than assuming that shaders are in the same location that the app is invoked from). It may be that in the future the shaders will be example specific. However, for the initial version the shaders just need to be placed into their own directory.

Create a directory for unit tests and a simple way of invoking the tests.

Create a Config class that can be passed to the App class to initialize it. The goal here is to provided a simple mechanism for extending the App class but also to make configuration data driven rather than hard coded.

The App class is intended to act as a controller that provides an interface for communicating with the renderer and interacting with the scene. It is not intended to provided file loading and support for formats X, Y, and Z. Currently, the App class loads data from an HDF5 file. Move this functionality into an example that extends the App class.

The current the version of mouse movement was a 5min hack to get something in place. The real solution needs to track the camera position correctly and map it to the (relative) mouse position from the initial click. This may require implementing slerp on the quaternion class.