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
First iteration scope: Simply help setting up the configuration file, and show e.g. what the resulting menu/overall layout will be, and for the plugins themselves you only show some styled placeholder divs (with e.g. plugin title).
We might want to do #357 first (especially @typing.overload there will provide useful information to the generated json schema, which will be valuable input to the GUI tool).
The text was updated successfully, but these errors were encountered:
To start the editor, we could perhaps see something like webviz config [existing-file-if-the-user-has.yaml], which opens a non-Dash based localhost server with the GUI editor? (webviz docs is an example of non-Dash based localhost server, in that case purely based on https://docsify.js.org/#/ + static server).
We implemented the first version of an editor which meets the above-mentioned requirements. The repo of the webviz-config-editor can be found here: github.com/equinor/webviz-config-editor. Further requirements should be posted directly in the respective repo. Hence, I am closing this issue. Any objections, @anders-kiaer?
A web GUI for help setting up (or modify existing)
webviz-config
configuration files would be useful.divs
(with e.g. plugin title).We might want to do #357 first (especially
@typing.overload
there will provide useful information to the generated json schema, which will be valuable input to the GUI tool).The text was updated successfully, but these errors were encountered: