Status on new GUI

I think one important thing that has been added later on is a button to switch between the two GUIs. Otherwise, you can only switch by editing config.xml manually.

Switch between GUIs? I thought it was based on the path
 If I call up http://localhost:8384/ I get the standard one, while http://localhost:8384/next-gen-gui/ gives me the new one?

Just for convenience, here is a build I made from the current Syncthing release: next-gen-gui-v1.28.0.zip (772.1 KB)

Unzip it under your GUI assets directory as the README states (slightly out of date
):

$ cd ~/.local/state/syncthing
$ mkdir -p gui/default
$ cd gui/default
$ unzip ~/next-gen-gui-v1.28.0.zip

IF you have user / password authentication configured, make sure to enable the sendBasicAuthPrompt setting, as the next-gen GUI doesn’t have an HTML login form. To do that, go to Actions > Advanced > GUI and enable the Send Basic Auth Prompt checkbox, then save. Otherwise, you’ll need to log into the standard GUI first before using the other one.

Then, open the new GUI variant under http://localhost:8384/next-gen-gui/.

2 Likes

Not sure about using the path, but there was a big problem when the other GUI was first added with the users being unable to switch back to the normal one. Then, the button was added to make switching back possible in next-gen-gui: Add button to restore default theme by calmh · Pull Request #7433 · syncthing/syncthing · GitHub.

That change is related to setting the theme though. I never thought of the next-gen-gui as being a theme in context of the standard GUI. How would you handle it like that?

Yeah, when compiled using --with-next-gen-gui, you can simply select it in the Web GUI as one of the themes.

Where is it “installed” in that case? When following the README instructions, it ends up as a subdirectory of default, thus can be reached under a corresponding sub-path (e.g. /next-gen-gui/). On the other hand, if you put it beside the default, light, dark etc. directories, it will be treated as a separate theme.

The latter is not really sensible IMHO. It actually prompted the mentioned change that there needs to be a way to switch back to the standard theme. But the next-gen-gui is not an actual “theme” in the first place, so reaching it under an alternative path is more suitable and allows to use both in parallel.

1 Like

It goes to gui/next-gen-gui. I personally find it quite interesting that you can simply add completely new GUIs as a theme, and then switch back and forth between them :slightly_smiling_face:.

Then at least the build script’s behavior is contradictory to the README description of the GUI. We should harmonize that, and I’m already collecting changes for a corresponding PR.

My clear favorite is having it inside the default folder, not as a separate theme. Because this way allows to use both in parallel, while the other variant only supports one at a time, exclusively.

Just for the record, the README is outdated. It was created in 2020, while the GUI was integrated into Syncthing proper in 2021 (via https://github.com/syncthing/syncthing/pull/7351).