We want to remove the old plotting widget and fully move to a plot-grid based architecture. There are a number of outstanding tasks:
The backbone to this would probably be a PlotOrchestrator (working title, time will tell if it should remain independent of PlottingController, but during the refactor we want the old mechanism to remain functional so adding a fresh class seems benefitial). Conceptually it would be something like:
@dataclass
class PlotTab:
name: UUID
title: str
plots: tuple[corner1, corner2, WorkflowId, OutputName, PlotterConfig] # better: dataclass(es)
class PlotOrchestrator:
_plots: list[PlotTab]
Just like JobOrchestrator stores WorkflowConfig, PlotOrchestrator would store plotter configs and plots tabs.
We want to remove the old plotting widget and fully move to a plot-grid based architecture. There are a number of outstanding tasks:
JobOrchestrator(Job orchestrator #540), which will move the UI towards a workflow-based approach.JobOrchestrator.The backbone to this would probably be a
PlotOrchestrator(working title, time will tell if it should remain independent ofPlottingController, but during the refactor we want the old mechanism to remain functional so adding a fresh class seems benefitial). Conceptually it would be something like:Just like
JobOrchestratorstoresWorkflowConfig,PlotOrchestratorwould store plotter configs and plots tabs.