Last modified: 2010-02-09 23:31:50 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T23862, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 21862 - Calculate remaining time when uploading
Calculate remaining time when uploading
Status: RESOLVED FIXED
Product: mwEmbed
Classification: Unclassified
Firefogg (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Neil Kandalgaonkar
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-12-16 10:54 UTC by Diaa
Modified: 2010-02-09 23:31 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Diaa 2009-12-16 10:54:11 UTC
Could there be an "Elapsed time:" and "Estimated time remaining:" in the dialogue box? Based on how fast each chunk is uploaded this should be calculable. A speed indicator would also be helpful.
Comment 1 Michael Dale 2009-12-16 19:36:32 UTC
This may be a good quick intro bug for Neil.  To give you a quick pointer you will want to look at mvBaseUpload.js & the updateProgress / updateProgressWin functions. These files are presently in the js2-work branch: http://svn.wikimedia.org/svnroot/mediawiki/branches/js2-work/phase3/js2/mwEmbed
Comment 2 Diaa 2009-12-24 22:08:37 UTC
Could u cc neil so he would see it ?
Comment 3 Michael Dale 2009-12-24 22:16:21 UTC
He apparently does not yet have an email address in the Bugzilla system. I will request that he gets that taken care of.

I added Guillaume should be helping tracking and assign media/commons related bugs. 
Comment 4 Neil Kandalgaonkar 2009-12-28 15:03:38 UTC
Just assigned it to myself.
Comment 5 Neil Kandalgaonkar 2010-01-06 18:22:15 UTC
OK, so, there wasn't really a spec on what it's supposed to look like, so I'm making one up:

|----------------------- Progress bar ---------------------------|
Percentage uploaded: N%          Estimated time remaining HH:MM:SS

I don't want to clutter the progress bar unnecessarily with three or four updating items. I'm going to assume the user really cares about when it will be done. The ideal thing is probably a display of when it will be done in local time conventions (like, "Finished around: 7:15pm"). As far as I know, neither JS nor jQuery gives us an easy human readable way to do that, so let's do the easy thing and just guestimate time remaining for now in HH:MM:SS.

Elapsed time and upload speed are more about troubleshooting problems. Let's set that aside for now. Obviously we will be tracking those internally, but maybe this could be info you could pop up, in a small link like "Upload stats", to get:

- Date.toLocaleString() of the time we started the upload
- elapsed time so far
- estimated time remaining
- Date.toLocaleString() of the time we estimate finishing the upload
- Average Kb/Seconds.

But, let's call that a nice-to-have for now.

At this moment I'm not sure what I want to do about multiple queued uploads, but I'm just starting to get the hang 
of how this is all put together.
Comment 6 Neil Kandalgaonkar 2010-01-06 18:33:03 UTC
Oh, also: Time remaining is probably only necessary if the upload lasts longer than a few seconds.

And the percentage upload is redundant with the displayed bar and could be eliminated, (unless this is somehow more accessible)?
Comment 7 Michael Dale 2010-01-06 22:15:32 UTC
I like to keep the visual progress bar. I would recommend just just swapping the text percentage for estimated time remaining. If its easy to do maybe put the text percentage inside the progress bar.

I would not worry about multiple queue items until we get the multiple file upload system working better. 

There are lots of other bugs and areas for improvement that could be focused on so definitely don't worry about exposing all the info or spending too much more time on this bug. 
Comment 8 Neil Kandalgaonkar 2010-02-09 23:30:44 UTC
Fixed in a sort of hacky way in revision #62206. Not as elaborate as my comments above.

A better way to do this is forthcoming.
Comment 9 Guillaume Paumier 2010-02-09 23:31:50 UTC
Dummy edit to get the handy link: r62206

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links