Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove or at least don't force the WebUI #8351

Closed
JagGillarVatten opened this issue Dec 22, 2024 · 8 comments
Closed

Remove or at least don't force the WebUI #8351

JagGillarVatten opened this issue Dec 22, 2024 · 8 comments
Assignees
Milestone

Comments

@JagGillarVatten
Copy link

JagGillarVatten commented Dec 22, 2024

It's slow, resource heavy, and is super clunky since it doesn't allow you to right click. I like it as a additional feature but not as the only option. Been downgrading to pre web-GUI releases cause I just can't stand it.
It's a downgrade in every single way.
I know this is kind of just me crying about some personal opinion but I genially love this program and the progress it has made.

@SpudmanWP
Copy link

I run it on a TrueNAS server in a Linux VM as the only app that runs. It'd be nice to not have to open the VM, run the app, and close the UI in order to run it. It'd be nice to set it to run at startup as a service?

btw, Super impressed with the performance of the new WebUI version.

@ichorid
Copy link
Contributor

ichorid commented Dec 26, 2024

@JagGillarVatten—I completely understand your sentiment, but as a former Tribler developer, I can tell you that supporting QT was literally hell, and it became utterly infeasible in the long run. Web tech is a bit clunkier, but it is 20x easier to support, debug, develop, distribute, and add new features. Peace ✌️

@qstokkink
Copy link
Contributor

@JagGillarVatten Thanks for the feedback! Adding a context menu should be possible in the web GUI: we just haven't implemented it. The GUI also shouldn't be slower: is there anything that feels slow to you in particular?

Regarding web GUI removal: we will be sticking with the web GUI for (at the very least) the near future. As @ichorid pointed out, we've burned many developers on GUI work. We're now down to 1.5 full-time developer (counting myself as 1/2 a developer) and it would slow down our project to a crawl otherwise.


@SpudmanWP you can run Tribler using the -s or --server option: this does not launch a GUI. Using it as a startup service should be a matter of adding tribler -s & to your bashrc.

@SpudmanWP
Copy link

@JagGillarVatten Thanks for the feedback! Adding a context menu should be possible in the web GUI: we just haven't implemented it. The GUI also shouldn't be slower: is there anything that feels slow to you in particular?

Regarding web GUI removal: we will be sticking with the web GUI for (at the very least) the near future. As @ichorid pointed out, we've burned many developers on GUI work. We're now down to 1.5 full-time developer (counting myself as 1/2 a developer) and it would slow down our project to a crawl otherwise.

@SpudmanWP you can run Tribler using the -s or --server option: this does not launch a GUI. Using it as a startup service should be a matter of adding tribler -s & to your bashrc.

Thanks, I'll try this soon.

@JagGillarVatten
Copy link
Author

Understood. Thanks for the insight.
.

@qstokkink qstokkink added this to the 8.2.0 milestone Feb 7, 2025
@qstokkink
Copy link
Contributor

I think we can look at adding a context menu for the 8.2.0 release.

@qstokkink qstokkink modified the milestones: 8.2.0, 8.1.0 Feb 18, 2025
@qstokkink
Copy link
Contributor

Actually, the context menu is already in #8443. Rescheduled for the 8.1.0 release.

@qstokkink
Copy link
Contributor

Merged 🎉 We now have a context menu again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

5 participants