A GUI needs to be created to allow a standardized way to control the application

The current thread design is naive at best. For each frame, a set of threads are spun up, each thread parses a section of the frame, then all of the threads shut down. These should be rewritten in a way that prevents the constant spin up and shut down of threads. When idle, care needs to be taken to prevent the threads from spinning.

Currently the code is built around a native OSx compilation. This should be enhanced to allow compilation on Linux distros as well as windows.

This will involve updating the lib and include paths in the CMakeLists.txt as well as some type checking when providing paths to the recording call.

Currently the resolution is compiled into the code as the gridsize tied to the OpenCvCam object. This should be made into a command line option to display the camera in different ways

The idea here is to create some framework around building these out so they work in combination. Fisheye might be a good one to start with. At the end it would be good to have the ability to chose either ascii, or fisheye or both.