Clarify download debug progress message#4713
Conversation
|
Hey there! Thanks for helping Mudlet improve. 🌟 Test versionsYou can directly test the changes here:
No need to install anything - just unzip and run. |
src/TLuaInterpreter.cpp
Outdated
| raiseDownloadProgressEvent(L, urlString, bytesDownloaded, totalBytes); | ||
| if (mudlet::debugMode) { | ||
| TDebug(QColor(Qt::white), QColor(Qt::blue)) << "\n" << bytesDownloaded << "/" << totalBytes << " for file " | ||
| TDebug(QColor(Qt::white), QColor(Qt::blue)) << "\n" << bytesDownloaded << "/" << totalBytes << " bytes downloaded for file " |
There was a problem hiding this comment.
Do we need the \n in that line as that is separating this line from the preceding message generated by the raiseDownloadProgressEvent(...) or can we not guarantee that that text will be there? If we cannot perhaps we should use:
| TDebug(QColor(Qt::white), QColor(Qt::blue)) << "\n" << bytesDownloaded << "/" << totalBytes << " bytes downloaded for file " | |
| TDebug(QColor(Qt::white), QColor(Qt::blue)) << "\nDownload progress: " << bytesDownloaded << " of: " << totalBytes << " bytes for file: " |
SlySven
left a comment
There was a problem hiding this comment.
How about something else that will stand alone better?
IMHO it is not so bad - and what if there are several large downloads going on. Does that message only show up at the end or after each "chunk" is received? If the latter then - depending on the size of the chunks - it might work quite well - or be horrible spammy... 😜 You could always change the beginning from: - "Download progress:"-
+ "DOWNLOAD:" |
|
I think we should keep it simple as it is. This PR is a super simple one fixing a problem, there was not enough info in the original message, but the message itself is fine. |
|
Hooray for bikeshedding! Let's review the texts in .. text maybe? Before jumping into code. STATUS QUO:
(Where URL and A and B are to be filled with variable values) VADI1:
This adds the hint "download" but still seems a bit arbitrary to me. SLYSVEN1:
I like the idea. Probably the SLYSVEN2:
This is going a bit further off-road and tries to close up to Here is my take: Let's name the function in the second line again! Also less verbose. KEBAP1:
..or to be even less verbose in the first line as well: KEBAP2:
|
|
I'd vote for |
|
To be honest there's a lot more other things that need doing, I don't have the energy for this. I just fixed a nonsensical message to make sense; if you'd like to change it entirely let's open up a separate discussion for this. Otherwise we won't go anywhere and the message still don't make sense in the release, is that a win? |
|
TBH In SlySven2 I was thinking of the "LUA" messages. And in both that and the prior one the I cannot recall the exact behaviour but I have a nasty suspicion that the second number is often not available in many download cases - so it might be simpler to only bother showing it if it is more than the first anyhow. I didn't realise this might be considered bikeshedding (and I didn't realise that was the definition - or that it had that negative a connotation!) Since we have a review process for everything - it is not surprising that we have different views - the input from others can avoid us merging in something that doesn't have some sort of consensus - KEBAPs is so-so I guess but "of" (for the file) is even shorter than "ready for" and doesn't necessarily imply that the file is complete. Now we have collected up these deckchairs then Vadim can tell/show us whether there is any change in his decision, we can rubber-stamp it and we can get on and steer this vessel away (hopefully) from the large chunks of ices out there. |
|
Let's go with |
SlySven
left a comment
There was a problem hiding this comment.
Lets suck this and crash and burn see.
* Clarify download progress message Co-authored-by: Kebap <kebap_spam@gmx.net>

Brief overview of PR changes/additions
Saw this message and had no idea what it means:
Turns out it was talking about download progress :)
Motivation for adding to Mudlet
Clearer debug message
Other info (issues closed, discussion etc)