-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
WebUi list of improvements that need to be made to the UI #9796
Comments
To this list, I would also add: Great list! And once again my sincere gratitude to @Piccirello for all the work he's put into the WebUI so far to keep it getting better. Legendary. |
This is a really comprehensive list. What’s exciting is several of these will be fixed soon by existing PRs. But definitely still a lot more work to be done. Could you switch your numbered list to a list of tasks? We can check off items as they’re completed. |
Great list, as a nox user having a rich webui is really important. Thx guys for keeping improving this functionality. |
Also: on iOS (and probably Android), disable autocorrect/capitalize for text input fields that shouldn’t have it (e.g. paths like /home/user/movies). Otherwise while typing things get automatically capitalized or corrected. I’ve seen this specifically with the ‘Save files to location’ field in ‘Upload local torrent’. |
Something that wasn't further discussed in the big #9752 (comment) but may be part of this improvements' list for stability in testing/trying new webUIs:
Or the other way around, the core webUI always be default on the base URL and the alternative under http://someIP:8099/altwebui/ Thoughts? |
I think the WebUI is fundamentally flawed because it means doubling the work of everything. I mean think of it like this, everything you add or remove or edit in the main UI you must repeat and do the same for the WebUI too. That feels like lifting two walls to stay on the same place. I don't mean that it is bad result no, but simply a bad investment of man-hour time. I think the correct approach is a single UI that is fully compatible & based on HTML5, something like the new UWP apps for example. Depending on the window or other factors those can, totally on the fly, morph into multiple UIs (cellphone, tablet and full desktop mode), all constructed under one singular code stream whilst being able to run inside a browser too because of HTML5 compatibility, meaning the WebUI would basically be a direct interface with the engine and depending on the size of the screen/window it would adapt (small-medium-full). And to reduce work, this project allows the removal of the medium size window (tablet-mode), leaving only small (cellphone) and full (desktop) which is more easy to maintain. Even if the suggested approach takes a more deep redesign of the main code, and much more initial man-hours to get any result at all, I say it's worth because it will pay for itself in terms of man-hours spared in the long run whilst also making the program future-proof. |
@Fernandk This sounds like a great vision, please feel free to open a PR. |
I've marked two right-click suggestions above as wontfix. I have no interest in disabling the browser's default right-click (context) menu when we don't have an alternative context menu to display. |
@Piccirello > @Fernandk This sounds like a great vision, please feel free to open a PR. I spent literally more than 20 minutes trying to open one, and it's not even the first time, but I couldn't get past the button "new pull request". The button "create new pull request" is greyed out and it keeps asking "Choose different branches or forks above to discuss and review changes." GitHub system for creating a new pull request is awfully unintuitive and retarded or I'm just really really dumb and I'm betting on the first one. To suggest a new feature or request should not be this hard. |
If you’d like to request a feature you need to open an issue. A PR is used for merging your existing code changes into qBittorrent (from your branch into qBittorrent master). |
I can't reproduce this one. Can someone post a screenshot? |
I actually think this is a bug on behalf of the GUI. The toolbar uses Edit: |
I do think these are consistent across the GUI and WebUI, and which you see just depends on the state of the torrent. |
May I suggest, when adding a torrent from the WebUI, to express the download and upload rate limits in KB/s instead of B/s? |
@simo1994 implemented by @jerrymakesjelly in #10618 |
Can we get the fix for file selection checked in soon? It's been ~7 months since I reported the issue and gave suggestions how to fix the event handling and it's still broken. edit: #10162 |
@xnoreq the PR is finally about to be merged, so the fix should land within the next few days. I should have applied the patch in a separate PR to avoid this scenario. Will note this for future bugs. |
I've opened a new issue to add the ability to modify the structure of a torrent when it's first added. This includes things like directory names and file names. #15718 |
Is this tracking ticket still being maintained ? |
I am not, if you like I could when I have time re-go through all the issues raised in this ticket. |
It may be valuable to x-ref with all the open |
The one feature on this list that I find useful and don't currently have a workaround for is the speed graph: sometimes it's useful for me when I'm trying to troubleshoot connection issues to see the history of DL/UL speed overnight, say, and in the Windows UI that's as simple as clicking a button. If it's possible at some point to add this to the web UI it would be a great help! Thanks. |
Anyone who is still following this, could you provide comments on this issue: #16239 |
It would work better for me if it this pane was actually shorter. As it is now, this pane doesn't fit within my laptop's browser window area without me zooming out. A couple alternatives would be to make all panes "wide" (as in in 16x9 aspect ratio to coincide with most monitors), or to move the Download button nearer to the top. |
@AceLewis do you mind bringing this list up to date ? |
@xavier2k6 should we open tickets for remaining tasks in OPs post? |
I don't use the WebUI much....only for testing purposes. However, we could review/x-ref the tasks here first against latest (No doubt there will be new additions too) I do know that there's no |
I don't use WebUI much either. So maybe we can get some folks that do to help ? |
Enough on the plate as it stands to get through before biting off anymore......leave it for now. |
I updated the list for 4.6 branch. Not sure if the PR i attached to |
Following up on my comment from nearly 6(!!) years ago - the vast majority of this list has been completed. I'm actively working on cookie management and the Add Torrent dialog, while a WebAPI now exists for torrent creation. After those three, the remaining items are incremental improvements. Such great progress from @qbittorrent/web-developers and other contributors during that time. |
I compared GUI with WebUI and there are still some notable features missing that should be added to the list:
Add torent dialog:
Some of the above could also be applied to RSS Downloader. Others:
|
This is a great list.
I've wanted this for so long - localstorage is an ugly hack. Perhaps via a separate WebAPI and configuration file? I suspect some of the core devs will have strong opinions on this. |
Better Mobil support is a must and probably the most important one too. |
@skomerko @Piccirello is anyone interested in updating OP's list with the new updates ? |
I've updated the OP with the newly listed items and tried to organize it a bit. |
This doesn't appear to be a goal of any of the web devs (myself included). For the best mobile support, I would recommend using a third party WebUI. |
qBittorrent version and Operating System
qBittorrent 4.1.3
Windows 10 (10.0.1xxxx)
What is the problem
The WebUI is not a replacement for the desktop UI
What is the expected behavior
WebUI to be as good as Qt UI
Steps to reproduce
Use WebUI
Extra info(if any)
I love the fact that the WebUI is very good, it is nearly a drop in replacement for the Qt UI. Piccirello is currently working on the WebUI so some of these may have been fixed when his commits are merged but I have made a list of the ones I have noticed. Correcting these would make it more viable to use qBittorrent with only a WebUI.
Remaining
Completed
Right click: should do nothing if no option is availible not open the normal right click menu(wontfix)General > Time active: different strings after time "seeded for XXX" vs "XXX this session"not an issueContent: Right click on column headers should result in nothing(wontfix)The text was updated successfully, but these errors were encountered: