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

Extend Web-Interface #763

Closed
JustMyGithub opened this issue Nov 15, 2018 · 6 comments
Closed

Extend Web-Interface #763

JustMyGithub opened this issue Nov 15, 2018 · 6 comments

Comments

@JustMyGithub
Copy link

I love transmission for its low footprint, but there are some features I really miss from utorrent 2.x:

  • show "added on" and "completed on" (what is age? creation of torrent? added on?)
  • tracker-category "none" or at least "sort-by-tracker
  • Web-UI: status-categories verify and error (qt gui has these view filters, but webui not)
  • Web-UI: show numbers next to the view filter in the dropdown-menus

Maybe I just don't find these features or there are other tickets about those that I have not found - if so, let me know :)

@chchia
Copy link

chchia commented Nov 16, 2018

I am using Transmission Remote GUI, you should give it a try.

@chchia
Copy link

chchia commented Nov 16, 2018

and i also recommend you to use
https://github.com/ronggang/transmission-web-control

to replace the internal webui.

@elboletaire
Copy link
Contributor

I also would love to see updates on the web gui, but I'm not really sure about what transmission developers have planed for it, as there are some PR related to the web gui which are not being accepted (like #490, #752, #559, #515, #349... there are many).

So... I'd like to take this opportunity to ask if there are any plans, at all, for the web UI? It makes sense for me to leave transmission only with the RPC protocol, and split the web ui into a different project (doing so, would be easier for others to collaborate).

@dnlzzxz

This comment has been minimized.

@elboletaire

This comment has been minimized.

@ckerr
Copy link
Member

ckerr commented Feb 25, 2022

I'm closing this ticket just for housekeeping's sake -- when a ticket has four unrelated issues, it's difficult to discuss them in the same comment thread, and the ticket can't be closed until all issues are fixed, even if they're unrelated.

So, nothing against the four issues described here; they just shouldn't all be in the same issue. Please file separate tickets for them ❤️

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

No branches or pull requests

5 participants