Bug 338560 - [ui] Plug-in install dialogs are have an unusably long status line
Summary: [ui] Plug-in install dialogs are have an unusably long status line
Status: CLOSED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.7   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2011-03-01 12:08 EST by Ian Taylor CLA
Modified: 2019-09-03 12:34 EDT (History)
5 users (show)

See Also:


Attachments
Screenshot showing overly long dialog text line (60.20 KB, image/jpeg)
2011-03-01 12:10 EST, Ian Taylor CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Taylor CLA 2011-03-01 12:08:22 EST
Build Identifier: 20100917-0705

When you are downloading a plugin, you get a message that appears and states the file that is being fetched, the download speed, and the source location.  Unfortunately, this information is all on one line, making it impossible to actually read.  To be able to read it, you must expand the dialog to a width that is insanely wide.

Reproducible: Always

Steps to Reproduce:
1.Help -> Install new software
2. Select a repo to download from, pick anything to install that is a moderate to large download.
3. Install the plugin.  
4. Observe the download status window that appears.  Its information is not readable unless you expand your window to be very wide.
Expected: The file, download progress, and download source messages are all on separate lines.
Comment 1 Ian Taylor CLA 2011-03-01 12:10:17 EST
Created attachment 190059 [details]
Screenshot showing overly long dialog text line

Attached a screenshot showing how wide you have to make the dialog in order to make its text visible.
if the items were each on a separate line, this would not be necessary.
Comment 2 Prakash Rangaraj CLA 2011-03-02 01:12:40 EST
All the information is provided in as the label of a job. I guess a separate view for the list of bundles being downloaded and the progress of each of them would be nice.
Comment 3 DJ Houghton CLA 2011-03-23 15:58:25 EDT
The p2 team could adjust some of the messages to be shorter but we can't predict the length of the URLs/JAR names that we will be trying to download so the messages could look good for one person, but horrible for others.

I think a more reasonable approach would be to generally allow line wrapping in the Status details dialog so that all Eclipse-based products can take advantage of this rather than everyone adjusting their message lengths.
Comment 4 DJ Houghton CLA 2011-03-24 09:15:21 EDT
I've created bug 340849 to address a generic solution so all bundles can display longer messages.

Currently we display the JAR name, the speed of the download, and the location of the JAR.

Which information do you suggest we remove?

Off the top of my head we may be able to string match and remove the JAR name from the URL if they are the same. (I think in most cases they are?) Is there any other information that you think the user might not need?
Comment 5 Henrik Lindberg CLA 2011-05-24 21:11:25 EDT
The problem with the truncation in the middle is that the truncated part most often is exactly what you want to see - the details are really only interesting when something is slow and not working. I always wanted the speed to be first, then the simplest possible name for the jar, and then the actual URL. It would be fine if the URL was right truncated (but visible on expand) as I think you are mostly interested in the host.

I also think there is an issue with multiple threads reporting status. It would be far better if it was possible to see details per download - the main status just showing average speed of all downloads and what is happening (start/finish perhaps), and details would show each URL and the speed. This would also provide opportunity to cancel an individual download (perhaps it is stuck or really really slow, and you want to force it to go to another mirror).

Just my 2c.
Comment 6 Ian Taylor CLA 2011-05-25 02:14:56 EDT
As the original filer of this bug, I agree with Henrik that if the dialog information was arranged in his suggested pattern and truncated on the right instead of in the middle, this dialog would be vastly more useful and readable.  

I still think that since there is tons of horizontal space on this dialog, wrapping (or specifically placing information on separate lines) might be preferable, but I would definitely say that if there is tons of work to make it wrap in a way that makes sense, and it's easy to change the dialog's information order and truncation style, then the 80/20 rule would say that you'd leave it as one line and and change the order and truncation, because it will still result in a vastly more readable dialog.

I just know that pretty much every time I install a plugin I see a dialog that says something like:

Fetching somelongjarName.jar ...  /a/bit/of/server/path/someLongJarName.jar

because the middle truncation and order of information basically ensures that the dialog begins and ends with the same information.  I then have to stretch my dialog box out to be super wide to see the useful parts.

The most important information to me is Download speed, how much data remains to be downloaded and which server I'm downloading from in that order.  The jar name doesn't matter much to me, as most plugins have many jar files and I don't care about the particulars of which file it's on, but I can see a case being made for it being more important than server name... either way it would be far more useful than the current dialog format.  

If you're wanting to trim some space, you could try getting rid of the word "Fetching" and losing some of the precision on the file sizes and download speeds.  I don't really need to know that I'm downloading 55.12MB at 110.86kB/s, 55MB at 110kB/s is more than accurate enough.
Comment 7 Thomas Watson CLA 2011-06-08 11:30:21 EDT
Move all 3.8 bugs to Juno.
Comment 8 Eclipse Genie CLA 2019-09-03 12:34:33 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.