Use `backendURL()` function to construct API and Add-on URLs, so that they
work regardless of what is serving the webapp (Flamenco Manager or the
Vite development server).
My way to get things working (I wouldn't call this a "solution" as I don't
know the root cause) was to emit two consecutive "reshuffled" events when
changing tabs in the job details, and to recalculate the table height when
the job type (so not the job itself, but its type info) is loaded.
After saving the configuration, show a message & restart the webapp.
The restarting is done after 2 seconds, to give the Manager some time to
restart after receiving the new config.
This just updates the config and saves it to `flamenco-manager.yaml`.
Saving the configuration doesn't restart the Manager yet, that's for
another commit.
This adds a `-wizard` CLI option to the Manager, which opens a webbrowser
and shows the First-Time Wizard to aid in configuration of Flamenco.
This is work in progress. The wizard is just one page, and doesn't save
anything yet to the configuration.
Add instructions to `web/README-static.md`, describing how to run the
static flamenco.io website locally.
Reviewed By: sybren
Differential Revision: https://developer.blender.org/D15426
This way, on OS that allow it, Flamenco can be added as home shortcut
and have the proper shortcut name, icon, theme color, and browser buttons.
Needs testing on how 'standalone' display looks on Android tablets. Perhaps
a more minimal version of the browser can be used instead ('minimal-ui').
Reload the webapp 60 minutes after keyboard/mouse activity.
Previously this was a hard 60 minutes after the webapp was loaded, which
means that it could happen while someone was actively working in the web
interface. This should now be prevented.
Use overlay overflow for compatible browsers (e.g. Chromium),
fallback to auto for non-compatible browsers (e.g. Firefox).
There should be no visible changes for Firefox users (tested on 101.0.1).
* Replace font-size with transform and inline-block display, this way the arrow
scales without making the line taller (which leads to misalignments or jumpy
UI when switching between transitional statuses.
* Do not use accent color, it gets lost with the surrounding colors in status names.
If we need to make this transition more prominent, we can use a subtle animation.
