The viewer class is a front-end that allows user to create a high-level application that collects the sensor data they want to view or process.
The viewer class is intended for a client application.
For each client application, there is a risk that there will be redundant capabilities that will be unidentified to us, since anyone will be able to use our library in the future.
To avoid these future redundancies,
we need to get closer to the graphical apis to minimise viewer-side client code.
We would only have to implement the front-end code to connect to the relevant rendering engines.
After that, the default rendering behaviour will be implemented in client/viewer3D.hpp and in the client/viewer3D folder.
We will be able to test the behaviour using tests.
The streamer and viewer clients will be as minimal as possible.
Users of the Viewer3D class will be able to modify the default rendering behaviour as they wish.
The viewer class is a front-end that allows user to create a high-level application that collects the sensor data they want to view or process. The viewer class is intended for a client application. For each client application, there is a risk that there will be redundant capabilities that will be unidentified to us, since anyone will be able to use our library in the future.
To avoid these future redundancies, we need to get closer to the graphical apis to minimise viewer-side client code. We would only have to implement the front-end code to connect to the relevant rendering engines. After that, the default rendering behaviour will be implemented in client/viewer3D.hpp and in the client/viewer3D folder. We will be able to test the behaviour using tests. The streamer and viewer clients will be as minimal as possible. Users of the Viewer3D class will be able to modify the default rendering behaviour as they wish.