Archived

This topic is now archived and is closed to further replies.

Directrix

WebUI v0.361 ready for testing

Recommended Posts

Btw 1.6.1 was released by BitTorrent, Inc. too. If the spyware FUD is the reason for banning the current version they are even bigger idiots...

@articuno1au:

You might be zipping up the folder. You shouldn't r-click on the folder and zip it. The files need to be in the root of the zip. Go inside the webui folder select all the files and folders and then r-click on one and copy to compressed folder. That should do the trick.

Share this post


Link to post
Share on other sites

Upgrade to 1.8.1. If you can't convince the tracker to allow 1.6.1 (despite the fact that 1.6.1 is released by BT), then find a tracker with more intelligent admins.

Any decent tracker allows it nowadays.

If anything, I'd be suspicious of THEIR motives, because it's possible to remotely exploit older clients.

Share this post


Link to post
Share on other sites
@NightThief: Which bug?

Adding torrents seems not working for me at all in the latest WebUI version, confirmed by a friend of mine too.

Edit: nevermind, I was pushing wrong "OK" button. Two "OK" buttons in one dialog is quite confusing.

Share this post


Link to post
Share on other sites

Yeah, I agree. I suppose adding a bit of space above and below the horizontal separator might make it slightly clearer.

Share this post


Link to post
Share on other sites

I'd suggest just combining all those input fields and having one set of "OK", "Cancel" buttons.

But I have no clue what for there are "Tracker URL" and especially "Cookies" fields. Usually I upload a .torrent file via that form.

Share this post


Link to post
Share on other sites

The file selection control isn't a standard input field, and the actions sent to the µTorrent backend aren't the same when adding via URL vs adding via .torrent file. So no, you can't simply merge the two.

Share this post


Link to post
Share on other sites

Yeah I know, I'm not talking about merging them, but just making them on one form and checking if we specified file to upload or tracker URL and choosing appropriate action. But as I told I don't know yet the use of those two fields.

Share this post


Link to post
Share on other sites

It's not tracker URL -- it's torrent URL. It's add torrent by URL. Combining them into one form would make little sense -- both methods are mutually exclusive. You can't add by both an uploaded .torrent and a URL in one form submission; it's one or the other. To be more correct, it's technically possible, but it's really bad design to mash two separate features and force them to work simultaneously every time the form is submitted.

There are other possibilities, like separating the dialogs, or adding some combobox/tab to switch between the two methods, but considering the sizes of the forms (they're small), separating them isn't any better. As long as a separation between the two methods is made clear (padding the space between them should, IMO, be sufficient), it's fine as is.

Share this post


Link to post
Share on other sites

Got it, thanks. So it works either by upload or by getting .torrent file via http (just like command in uT), WebUI backend can choose which action to take by the submitted data. It would simplify that dialog.

edit: OK, that makes sense. Lets see what Directrix thinks about above thoughts :)

Share this post


Link to post
Share on other sites

No... One is a multipart form upload using POST, the other is a simple HTTP GET request. You don't mash them together; the two mechanisms are completely different. There's no reason the backend should try to interpret the input in a command where the inputs are wildly different. If a UI wants to use a specific method, what happens when the backend misinterprets? The UI won't get what it wants. So that's why the two actions need to be separated, and the UI should figure out which exact command the backend should execute instead.

Share this post


Link to post
Share on other sites

Yeah it would involve setting the method and a variety of fields in that little form based on wether the tracker URL was filled in or the file field was used. That is what they would call bloat. Especially if with a bit more visual flashiness it can be made clear to the user.

Share this post


Link to post
Share on other sites

Do you think in this build we can get the no of peers in the webui (in expanded view) such as flag and ip address and client(s) of other peers?

Share this post


Link to post
Share on other sites

That could be added I think, unfortunately I feel it should be disabled by default. With the webui pumping data out already at 100s of bytes per loaded torrent... I think much more data would negate the usefulness of a ... web front-end. If you want ALL of the trimmings of the GUI, don't use the webui.

Share this post


Link to post
Share on other sites

It's been requested before anyhow. Seeing the peers, while a novelty, isn't all that useful in the context of a remote control UI.

Share this post


Link to post
Share on other sites

Ok is it usual for the webui not to display all of the seed numbers properly when the torrent is seeding but no one is downloading the torrent off you?

I am meaning when no one is downloading of me i get 0 seeds it says but then i check on utorrent itself it has about 56.

But when someone is leeching of me it displays the no of seeds and peers perfectly.

Is this a bug or should i just expect this. (it is not major but still would like to know if some 1 else apart from me is seeding the file without going back to the program itself.

Share this post


Link to post
Share on other sites

I try to remove "force start" (following this topic http://forum.utorrent.com/viewtopic.php?id=36945)

"You'll have to find and remove all instances of ContextMenu.add(["Force Start", ...]) from script.js, like:

ContextMenu.add(["Force Start"]);

ContextMenu.add(["Force Start","utWebUI.ForceStart()"]);

"

But i can't find script.js in webui 0.361.

Help me please

Thank you in advance.

Share this post


Link to post
Share on other sites

That's because that suggestion was for an old version of WebUI, not v0.361...

In webui.js, remove:

if(!(A&64)){ContextMenu.add([lang[CONST.ML_FORCE_START]])}else{ContextMenu.add(D)}

Then replace webui.js. If you see webui.js.gz, extract the webui.js from the file, edit that extracted file, then re-add webui.js into webui.zip and remove webui.js.gz from the zip file.

Share this post


Link to post
Share on other sites

The backend's handling of the requests have not changed. That is, the option is handled through the UI, not the backend.

Share this post


Link to post
Share on other sites

Got another problem, the estimated time in ut and webui are different (way too much for me) - example:

UT:

ut.jpg

WEBUI:

webui.jpg

I suppose that problem could be huge size of torrent which is 107GB...

Share this post


Link to post
Share on other sites

Known issue. IINM, the backend sends an instantaneous ETA, not the sliding averaged ETA -- hence the discrepancy.

I'll need to research before I post next time :P

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.