Expanding on existing product classes and the experience they provide

The experience that provides is heavily state-driven, which means that at a given point in time, you can only modify one product class. The was developed in this manner to provide a guided experience out of the bo

Having said that, we try our best to allow our clients to build customizable UI around our solutions if they wish to. This guide outlines some of the ways you can provide a slightly different experience around the current system.

Here is how it goes:

1. To move the camera manually to a new position when you are in "both" state, use this call

EPIGRAPH_CONFIGURATOR.api.moveCameraToCameraViewById(<a_valid_camera_view_id>); 
// <a_valid_camera_view_id> explained below

2. A "camera view" consists of a predefined camera position & settings in the scene. These "camera views" are provided to you by Epigraph to ease the process of setting them up, since attaining and providing all of the required information by yourself can be tedious and time-consuming without prior knowledge of the camera systems in 3D engines.
   To retrieve a list of all available camera views, you could use the method below.

EPIGRAPH_CONFIGURATOR.api.getAllCameraViewIds();
// ["front-view", "side-view"]

📘

Missing Camera Views

If there is a view that you feel is missing or you need additional camera views, please reach out to the Epigraph team and we can work together to create new camera views.

3. Once you have placed a camera in a position you are happy with, you can switch product classes and variants by passing an additional flag into the following methods which will stop the default camera action from taking place:

EPIGRAPH_CONFIGURATOR.api.makeProductIdActiveInCurrentClass("myCustomCameraView", true); 
// the second parameter is called "skipCamera" and will switch product without affecting the view.

4. Below you will find a list of the methods that support the "skipCamera" parameter (All default to false):
   • makeNextProductClassActive(skipCamera?): void
   • makePreviousProductClassActive(skipCamera?): void
   • makeProductClassIdActive(productClassId, skipCamera?): void
   • makeProductClassIndexActive(productClassIndex, skipCamera?): void
   • makeProductIdActiveInCurrentClass(productId, skipCamera?, blockScene?): void