Skip to content

Latest commit

 

History

History
109 lines (80 loc) · 8.03 KB

event-display.md

File metadata and controls

109 lines (80 loc) · 8.03 KB
Raw

Phoenix event display

Introduction

The EventDisplay class is the primary building block of Phoenix. As in the Phoenix architecture, it interconnects the ThreeManager, UIManager and EventDataLoader. It works as the primary endpoint for accessing all Phoenix functions.

See the API docs for EventDisplay to have a deeper look at the available functions.

Modularity and architectural overview

As specified in the Phoenix architecture, the EventDisplay depends on some underlying managers to perform operations. Almost none of the functions of the EventDisplay are implemented directly in the EventDisplay. Instead the EventDisplay works as an intermediate interface that uses different managers and services to perform the relevant operations and interconnects them.
This architectural approach helps in maintaining the modularity of Phoenix and makes it easier to add new functionality in isolation if needed.

The modular and extendable nature of Phoenix is not limited to just the EventDisplay. The managers are also further divided into sub managers each of which is responsible for handling and maintaining different aspects and features.

ThreeManager

The ThreeManager is responsible for performing all three.js related functions. Any feature that depends on the three.js library is implemented through the ThreeManager. Since Phoenix has a lot of features implemented through three.js, the ThreeManager is further divided into sub managers which have different roles.

Here is a list of sub managers of ThreeManager:

  • AnimationsManager
    Responsible for animation related operations. For example, animating the camera through the event.
  • ColorManager
    Provides functionality for managing coloring of objects in the scene.
  • ControlsManager
    Manages all controls related functionality which includes the camera, orbit controls and zoom controls.
  • EffectsManager
    Used for managing event display effects like the outline pass for selected object.
  • ExportManager
    Manages export related functions like exporting the event display to an .obj file or to the .phnx (Phoenix scene) file.
  • ImportManager
    Manages import related functions like importing different types of 3D geometries (.gltf, .root, .obj, etc.) or event data (.json, .xml, etc.).
  • RendererManager
    Manages three.js renderers used by Phoenix including both the main and overlay renderer (used in the overlay view).
  • SceneManager
    Used to manage three.js scene related operations like traversing through the scene, applying color or opacity to 3D objects, managing scene lights, etc.
  • SelectionManager
    Manages selection functionality of the event display like applying outline pass to a selected object or getting selected object info for the object selection overlay.
  • XRManager
    Provides common functionality of AR/VR like setting up the session and XR camera.
    • ARManager
      Extended from XRManager. Used to manage AR related functions like starting an AR session and showing overlay in AR mode.
    • VRManager
      Extended from XRManager. Used to manage VR related functions like setting up VR controls and movement.

Currently the sub managers are not big enough to be divided into multiple parts. However, if at some point their code gets large, it should be further divided.

UIManager

The UIManager is responsible for all the UI aspects of the EventDisplay. This includes the Phoenix menu, dat.GUI menu, stats UI, etc.

It takes care of tasks like:

  • Adding configuration options to Phoenix UI on loading geometry or event data.
  • Setting the UI color theme to dark or light.
  • Applying clipping to geometries.
  • Linking UI menu options with the EventDisplay.
  • Configuring different color options for event data.
  • etc.

It also has ColorOptions which contains logic to color event data.

PhoenixUI

PhoenixUI is used as a common interface for implementing UI menus in Phoenix. It currently has the following implementations:

  • DatGUIMenuUI Contains functions for setting up all the options in dat.GUI menu.
  • PhoenixMenuUI
    Contains functions for setting up all the options in Phoenix menu.

PhoenixMenuNode

The PhoenixMenuNode is a class that maintains all the options of Phoenix menu at the program level. It doesn't implement the UI for Phoenix menu but contains all the logic.
It is designed to be adaptable to custom UIs. This class can be used to create a custom Phoenix menu like interface in any kind of frontend framework.

For an overview, it contains functions for:

  • Adding children (of the same PhoenixMenuNode type) to a node.
  • Adding custom configuration of different types (like checkbox, slider, button, label, etc.) to a node.
  • Getting and loading the state of a node.
  • Removing a single child node, current node, or all child nodes.
  • Finding a node in tree by name, or create one if not found.
  • etc.

Miscellaneous managers

These are some independent managers not part of the ThreeManager or UIManager but used inside the EventDisplay.

  • LoadingManager
    Maintains a list of loadable items with addable callbacks that are called when the loading of an item completes.
  • StateManager
    Manages the state of the EventDisplay including the Phoenix menu state, camera state and clipping state. The state can be saved to a file and loaded later.
  • URLOptionsManager
    Manages EventDisplay options available through the URL like loading an event through the URL (file & type) or hiding overlay widgets (hideWidgets).

Event data loaders

See Event data loader for details.