Add missing features from Qt UI to web UI #35

Author

Owner

@koolfy commented on GitHub (Aug 22, 2012):

This would be a good place to track the progression of the WebUI catching the QT client features.

@koolfy commented on GitHub (Aug 22, 2012): This would be a good place to track the progression of the WebUI catching the QT client features.

deekerman commented

Author

Owner

@Gruffi commented on GitHub (Aug 26, 2012):

If i'm correct there is no RSS in nox either. Would love to have that feature :)

@Gruffi commented on GitHub (Aug 26, 2012): If i'm correct there is no RSS in nox either. Would love to have that feature :)

deekerman commented

Author

Owner

@leandrocosta commented on GitHub (Oct 24, 2012):

Also: change destination folder for each torrent.

@leandrocosta commented on GitHub (Oct 24, 2012): Also: change destination folder for each torrent.

deekerman commented

Author

Owner

@MPW1412 commented on GitHub (Nov 25, 2012):

Wouldn't it be possible to completly seperate the ui from the torrent-client? So that u have running the client and can then login from the webui or either from the client? Probably that would be more interessting for linux users.

@MPW1412 commented on GitHub (Nov 25, 2012): Wouldn't it be possible to completly seperate the ui from the torrent-client? So that u have running the client and can then login from the webui or either from the client? Probably that would be more interessting for linux users.

deekerman commented

Author

Owner

@frei0 commented on GitHub (Nov 26, 2012):

This is possible with the qbittorrent-nox package
On Nov 25, 2012 4:09 PM, "MPW1412" notifications@github.com wrote:

Wouldn't it be possible to completly seperate the ui from the
torrent-client? So that u have running the client and can then login from
the webui or either from the client? Probably that would be more
interessting for linux users.

—
Reply to this email directly or view it on GitHubhttps://github.com/qbittorrent/qBittorrent/issues/44#issuecomment-10700836.

@frei0 commented on GitHub (Nov 26, 2012): This is possible with the qbittorrent-nox package On Nov 25, 2012 4:09 PM, "MPW1412" notifications@github.com wrote: > Wouldn't it be possible to completly seperate the ui from the > torrent-client? So that u have running the client and can then login from > the webui or either from the client? Probably that would be more > interessting for linux users. > > — > Reply to this email directly or view it on GitHubhttps://github.com/qbittorrent/qBittorrent/issues/44#issuecomment-10700836.

deekerman commented

Author

Owner

@MPW1412 commented on GitHub (Nov 26, 2012):

Only partially: You can't login from the qBittorrent-Gui to qBittorrent-nox, because it doesn't start a second instance.

@MPW1412 commented on GitHub (Nov 26, 2012): Only partially: You can't login from the qBittorrent-Gui to qBittorrent-nox, because it doesn't start a second instance.

deekerman commented

Author

Owner

@s4zando commented on GitHub (Sep 22, 2013):

+1 Please add RSS capabilities to qbittorrent-nox so that it has feature parity with qBittorrent with X windows.

@s4zando commented on GitHub (Sep 22, 2013): +1 Please add RSS capabilities to qbittorrent-nox so that it has feature parity with qBittorrent with X windows.

deekerman commented

Author

Owner

@dmitry commented on GitHub (Jan 12, 2014):

Download by sequential order was started in: #640

@dmitry commented on GitHub (Jan 12, 2014): Download by sequential order was started in: #640

deekerman commented

Author

Owner

@fbarriga commented on GitHub (Jan 4, 2015):

[webui] [wishlist] Torrent labels in WebUI: #648

@fbarriga commented on GitHub (Jan 4, 2015): [webui] [wishlist] Torrent labels in WebUI: #648

deekerman commented

Author

Owner

@sudisk commented on GitHub (Feb 25, 2015):

I'm not much of a web developer, but I am working on an Android app. There are a few things that I would find interesting to add to the web API:

Being able to select the data to be returned in the torrent list to avoid bandwith waste when lots of torrents,
(Corollary) Retrieve the full list of available fields to choose from,
- that allows for custom columns in table view or for sorting without loading all the informations from all torrents
- it makes it easier for some stats computation,
(Corollary) Select the fields to be included in the torrent details, so that depending on what the user is doing, we might even request different bits of data at a different time.
Filtering: it would be nice to have a "transferring" filter that would only return torrents currently uploading OR downloading, and not "active" torrents with zero transfer rate.
Customization: add all actions from the native UI to the Web UI, including ratio and location.
API version management: be able to manage Web API evolutions and warn client developers about any EOL management of a particular API version.
Compatibility: the new APIs should not break existing behaviour.

My C++ skills are old (as in not used for a very long time) and I do not want to bork everything but I may give it a try myself. Don't hope much for my elder fingers' contribution though.

@sudisk commented on GitHub (Feb 25, 2015): I'm not much of a web developer, but I am working on an Android app. There are a few things that I would find interesting to add to the web API: - Being able to select the data to be returned in the torrent list to avoid bandwith waste when lots of torrents, - (Corollary) Retrieve the full list of available fields to choose from, - that allows for custom columns in table view or for sorting without loading _all_ the informations from all torrents - it makes it easier for some stats computation, - (Corollary) Select the fields to be included in the torrent details, so that depending on what the user is doing, we might even request different bits of data at a different time. - Filtering: it would be nice to have a "transferring" filter that would only return torrents currently uploading OR downloading, and not "active" torrents with zero transfer rate. - Customization: add all actions from the native UI to the Web UI, including ratio and location. - API version management: be able to manage Web API evolutions and warn client developers about any EOL management of a particular API version. - Compatibility: the new APIs should not break existing behaviour. My C++ skills are _old_ (as in not used for a very long time) and I do not want to bork everything but I may give it a try myself. Don't hope much for my elder fingers' contribution though.

deekerman commented

Author

Owner

@pmzqla commented on GitHub (Feb 25, 2015):

@sudisk
The documentation must be updated, but there have been quite a few changes in the API (of qBittorrent 3.2.0, which is still in alpha stage) and some of your requests had already been implemented. Although the official documentation is not updated, I wrote a simple txt file with the changes to have a better overview of the changes and make updating the official documentation simpler.

See this (and a message after that regarding seq_dl and f_l_piece_prio) for more info.

@pmzqla commented on GitHub (Feb 25, 2015): @sudisk The documentation must be updated, but there have been quite a few changes in the API (of qBittorrent 3.2.0, which is still in alpha stage) and some of your requests had already been implemented. Although the official documentation is not updated, I wrote a simple txt file with the changes to have a better overview of the changes and make updating the official documentation simpler. See <a href="https://github.com/qbittorrent/qBittorrent/issues/2457#issuecomment-71479905">this</a> (and a message after that regarding `seq_dl` and `f_l_piece_prio`) for more info.

deekerman commented

Author

Owner

@JustMaier commented on GitHub (May 15, 2015):

+1 for label support via web ui and api.

@JustMaier commented on GitHub (May 15, 2015): +1 for `label` support via web ui and api.

deekerman commented

Author

Owner

@Rouzax commented on GitHub (May 15, 2015):

This is the only reason I still need to stick with uTorrent, so this would really be appreciated.

@Rouzax commented on GitHub (May 15, 2015): This is the only reason I still need to stick with uTorrent, so this would really be appreciated.

deekerman commented

Author

Owner

@Jaerin commented on GitHub (May 15, 2015):

Agreed Label support via the API/web

@Jaerin commented on GitHub (May 15, 2015): Agreed Label support via the API/web

deekerman commented

Author

Owner

@Rouzax commented on GitHub (Jun 17, 2015):

What is the current status of setting labels through the API?

@Rouzax commented on GitHub (Jun 17, 2015): What is the current status of setting labels through the API?

deekerman commented

Author

Owner

@ngosang commented on GitHub (Jun 17, 2015):

What is the current status of setting labels through the API?

The work is almost done #2558 but some changes are needed. It may take time.

@ngosang commented on GitHub (Jun 17, 2015): > What is the current status of setting labels through the API? The work is almost done #2558 but some changes are needed. It may take time.

deekerman commented

Author

Owner

@ngosang commented on GitHub (Jun 23, 2015):

Several features added #3279.

@ngosang commented on GitHub (Jun 23, 2015): Several features added #3279.

deekerman commented

Author

Owner

@Rouzax commented on GitHub (Aug 18, 2015):

@ngosang I see several PR and closed issues. Does that mean that setting the labels through the API is implemented?

@Rouzax commented on GitHub (Aug 18, 2015): @ngosang I see several PR and closed issues. Does that mean that setting the labels through the API is implemented?

deekerman commented

Author

Owner

@ngosang commented on GitHub (Aug 23, 2015):

Does that mean that setting the labels through the API is implemented?

@Rouzax Yes, in #3444 but isn't merged yet. I think it will be in the next release.

@ngosang commented on GitHub (Aug 23, 2015): > Does that mean that setting the labels through the API is implemented? @Rouzax Yes, in #3444 but isn't merged yet. I think it will be in the next release.

deekerman commented

Author

Owner

@lgallard commented on GitHub (Dec 8, 2015):

Hi guys,

Are you working on setting labels through the API?

@lgallard commented on GitHub (Dec 8, 2015): Hi guys, Are you working on setting labels through the API?

deekerman commented

Author

Owner

@ngosang commented on GitHub (Dec 10, 2015):

@lgallard since version 3.3.0 you can set labels through the API.

@ngosang commented on GitHub (Dec 10, 2015): @lgallard since version 3.3.0 you can set labels through the API.

deekerman commented

Author

Owner

@lgallard commented on GitHub (Dec 11, 2015):

@ngosang Where can I check the documentation? Because the WebAPI documentation has not references in how to add or remove labels using the API.

Thanks in advance!

@lgallard commented on GitHub (Dec 11, 2015): @ngosang Where can I check the documentation? Because the [WebAPI documentation](https://github.com/qbittorrent/qBittorrent/wiki/WebUI-API-Documentation) has not references in how to add or remove labels using the API. Thanks in advance!

deekerman commented

Author

Owner

@pmzqla commented on GitHub (Dec 11, 2015):

It needs to be updated, but if I'm not wrong it should be:

POST command/setLabel

hashes=HASH1|HASH2|...&label=LABEL_NAME

You can't delete labels, unless I missed something.

EDIT: Spotted a bug while testing this: https://github.com/qbittorrent/qBittorrent/pull/4341.

@pmzqla commented on GitHub (Dec 11, 2015): It needs to be updated, but if I'm not wrong it should be: ``` POST command/setLabel hashes=HASH1|HASH2|...&label=LABEL_NAME ``` You can't delete labels, unless I missed something. EDIT: Spotted a bug while testing this: https://github.com/qbittorrent/qBittorrent/pull/4341.

deekerman commented

Author

Owner

@lgallard commented on GitHub (Feb 2, 2016):

@pmzqla @ngosang Any advance on deleting torrent labels through the API?

@lgallard commented on GitHub (Feb 2, 2016): @pmzqla @ngosang Any advance on deleting torrent labels through the API?

deekerman commented

Author

Owner

@ngosang commented on GitHub (Feb 3, 2016):

@lgallard Implemented in #4661 but not merged yet.

@ngosang commented on GitHub (Feb 3, 2016): @lgallard Implemented in #4661 but not merged yet.

deekerman commented

Author

Owner

@lgallard commented on GitHub (Apr 15, 2016):

@pmzqla @ngosang I can't find any reference in the code about:

POST command/setLabel

hashes=HASH1|HASH2|...&label=LABEL_NAME

Are you sure it is available since 3.3.0?

On the other hand? Do you think that deleting/setting of labels through the API will be in 3.3.5? Because I coulnd't find any mention in milestone v3.3.5

Regards,

@lgallard commented on GitHub (Apr 15, 2016): @pmzqla @ngosang I can't find any reference in the code about: ``` POST command/setLabel hashes=HASH1|HASH2|...&label=LABEL_NAME ``` Are you sure it is available since 3.3.0? On the other hand? Do you think that deleting/setting of labels through the API will be in 3.3.5? Because I coulnd't find any mention in [milestone v3.3.5](https://github.com/qbittorrent/qBittorrent/milestones/v3.3.5) Regards,

deekerman commented

Author

Owner

@ngosang commented on GitHub (Apr 16, 2016):

I can't find any reference in the code about:

In the source code or in the API documentation? I updated the API doc => https://github.com/qbittorrent/qBittorrent/wiki/WebUI-API-Documentation#set-torrent-label

Are you sure it is available since 3.3.0?

Yes.

Do you think that deleting/setting of labels through the API will be in 3.3.5?

Yes #4661.

@lgallard Next time open a new issue.

@ngosang commented on GitHub (Apr 16, 2016): > I can't find any reference in the code about: In the source code or in the API documentation? I updated the API doc => https://github.com/qbittorrent/qBittorrent/wiki/WebUI-API-Documentation#set-torrent-label > Are you sure it is available since 3.3.0? Yes. > Do you think that deleting/setting of labels through the API will be in 3.3.5? Yes #4661. @lgallard Next time open a new issue.

deekerman commented

Author

Owner

@lgallard commented on GitHub (Apr 18, 2016):

@ngosang thanks for the reply.

I will open a new issue next time!

Regards,

@lgallard commented on GitHub (Apr 18, 2016): @ngosang thanks for the reply. I will open a new issue next time! Regards,

deekerman commented