It is a bit tedious to run Python scripts to directly manipulate component state. We should have a dashboard that allows users to directly manipulate state.
The landing page: a sidebar of components in the application. If a component is clicked, the main page shows a list of all instances of that component (with a search bar to search for the specific instance).
Clicking on the component instance to edit should open a popup. If the state has a table, we can display the table as an editable set of values. Otherwise the user can directly edit values. We will preserve the type.
To run the dashboard, the user should simply run some command like motion dashboard, which will spin up the dashboard in their browser.
It is a bit tedious to run Python scripts to directly manipulate component state. We should have a dashboard that allows users to directly manipulate state.
The landing page: a sidebar of components in the application. If a component is clicked, the main page shows a list of all instances of that component (with a search bar to search for the specific instance).
Clicking on the component instance to edit should open a popup. If the state has a table, we can display the table as an editable set of values. Otherwise the user can directly edit values. We will preserve the type.
To run the dashboard, the user should simply run some command like
motion dashboard, which will spin up the dashboard in their browser.