You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the View Events flyout is specific to PointInTimeEventsVisLayers. The way the flyout is laid out requires tight integration with the base visualization, and the sub-charts below showing each of the VisLayer events. Because of this tight integration, the implementation lives in VisAugmenter plugin in OSD, in order to keep things consistent, such that any plugins that emit events on top of a particular visualization is shown correctly and lined up such that the correlation shown within the flyout looks correct. This also gives us the benefit of all plugins that emit these events, will be organized and shown in a consistent manner for all plugins.
For integrations with future plugins and other potential VisLayer types that may be introduced, we may want to have VisAugmenter have less control over the rendering, and instead allow plugins themselves to control how a deep-dive into the VisLayer may look. For example, for looking at details of forecasting results on top of a visualization, we may want to just show an empty panel at the VisAugmenter level, and allow the plugin responsible for producing the forecasted results, show how they may want to provide more details or a more thorough breakdown of those results.
This can be done using UIActions, such that VisAugmenter could use triggers such that plugins could have actions associated with them to perform different actions (e.g., trigger with context including the visualization to allow the plugin to re-render the visualization along with a detailed breakdown of the forecasted data).
The text was updated successfully, but these errors were encountered:
Currently, the View Events flyout is specific to
PointInTimeEventsVisLayer
s. The way the flyout is laid out requires tight integration with the base visualization, and the sub-charts below showing each of theVisLayer
events. Because of this tight integration, the implementation lives inVisAugmenter
plugin in OSD, in order to keep things consistent, such that any plugins that emit events on top of a particular visualization is shown correctly and lined up such that the correlation shown within the flyout looks correct. This also gives us the benefit of all plugins that emit these events, will be organized and shown in a consistent manner for all plugins.For integrations with future plugins and other potential
VisLayer
types that may be introduced, we may want to haveVisAugmenter
have less control over the rendering, and instead allow plugins themselves to control how a deep-dive into theVisLayer
may look. For example, for looking at details of forecasting results on top of a visualization, we may want to just show an empty panel at theVisAugmenter
level, and allow the plugin responsible for producing the forecasted results, show how they may want to provide more details or a more thorough breakdown of those results.This can be done using
UIActions,
such thatVisAugmenter
could use triggers such that plugins could have actions associated with them to perform different actions (e.g., trigger with context including the visualization to allow the plugin to re-render the visualization along with a detailed breakdown of the forecasted data).The text was updated successfully, but these errors were encountered: