Description
Our current MVP code architecture comprises of unnecessary classes and confusing scripts that all depend on one another. This is bad object-oriented programming design as a single break may cause a chain of failures.
Thus, the aim is to restructure our codes and scripts into 3 major categories:
Core - This comprises of the main functionalities of our plugin, namely the camera follow, video record, record trigger, and avatar.
Utils - This includes extra features that are not demonstrated in our core scripts, such as a live feed plane (that developers can use for debugging purposes).
Demo - This will consist of all the code that is used in our demo scene. These will be built upon code that is on our core features.
Task List
[x] Develop a technical style guide that includes a chosen commenting and naming convention
[x] Make a core folder that includes all codes used in our main features of our plugin
[x] Make a utils folder that includes the extra features of our plugin
[x] Implement ShareVR.Core.CameraController. Assigned to @adammy123
[x] Implement ShareVR.Core.InputManager. We will implement two ways including keyboard trigger and Vive controller input trigger. Assigned to @chenchen2015
[x] Implement ShareVR.Core.AvatarController. Assigned to @adammy123
[x] Implement ShareVR.Core.RecordManager. Assigned to @chenchen2015
Description Our current MVP code architecture comprises of unnecessary classes and confusing scripts that all depend on one another. This is bad object-oriented programming design as a single break may cause a chain of failures.
Thus, the aim is to restructure our codes and scripts into 3 major categories:
Task List
Related Version SDK v0.1