Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 369387

Summary: Progress result in the right bottom corner does not attract attention
Product: [ECD] Orion Reporter: Szymon Brandys <Szymon.Brandys>
Component: ClientAssignee: Susan McCourt <susan>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: bokowski, john.arthorne, malgorzata.tomczyk, simon_kaegi, susan, tomasz.zarna
Version: unspecified   
Target Milestone: 0.4 RC1   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Szymon Brandys CLA 2012-01-23 09:33:16 EST
I was testing cherry-pick on the git commit page. I clicked the action once and nothing happened. Then the second and third time when I realized that the status is shown in the right bottom corner. For some reason I was looking for a message around the cherry-pick action in the toolbar. I think that the right bottom corner is fine for the operation result but we need to draw the user attention to it.
Comment 1 Szymon Brandys CLA 2012-01-23 09:38:08 EST
Moreover when I started clicking the cherry-pick action I wasn't really sure whether I clicked it or not. This is because the action is presented as a link which is not changed on click. Just on hover.
Comment 2 John Arthorne CLA 2012-01-23 09:48:39 EST
I also noticed the "Server Operations" link today, and it seems to get lost next to the privacy policy, terms of use, etc. My first guess would be this is a link to policy or information about server operations (scheduled downtime, announcements, etc). Do we even need a link to the operations list when nothing is running (Eclipse doesn't)? Maybe when there is nothing running the progress message should just be a hyperlink that says "<name of last task> completed". Clicking that message would take you to the complete list?
Comment 3 Susan McCourt CLA 2012-01-23 12:07:48 EST
Another time I forget to look down in the footer is when I do a find/replace in the editor.  I'm so used to looking at the top for the red "not found".  I was trying to figure out if the problem was one of retraining myself or more.  I agree we need to call more attention to it.

(In reply to comment #2)
> Do we even need a link to the operations list when nothing
> is running (Eclipse doesn't)? 

In eclipse you can "show view" on the jobs view so you can always get to it.  I think we need to surface it somewhere.  Another idea was the user menu (it seemed too prominent in the user popup but in a menu format maybe better?)

> Maybe when there is nothing running the progress
> message should just be a hyperlink that says "<name of last task> completed".
> Clicking that message would take you to the complete list?

Interesting.  Gosia, what do you think?
Comment 4 Susan McCourt CLA 2012-01-23 12:11:42 EST
(In reply to comment #1)
> Moreover when I started clicking the cherry-pick action I wasn't really sure
> whether I clicked it or not. This is because the action is presented as a link
> which is not changed on click. Just on hover.

I thought we had this in a bug already but couldn't easily find it.  I added a comment to bug 360986.  It's up in the air right now what our command treatment is in the various toolbars (link, button, icons, etc.) but whatever we do needs to have a good hit feedback.
Comment 5 Susan McCourt CLA 2012-01-23 13:27:30 EST
Boris thinks that having progress/status in the footer makes us look more "IDE-ish" and less webby.  We've always pinned the footer but it's getting more noticeable now.
Comment 6 Susan McCourt CLA 2012-01-23 14:15:20 EST
one of Linda's initial ideas was to have the footer grow (slide up) when there is a notification message.  This would keep the footer skinnier, too, but doesn't allow room for John's idea (repurposing the progress area for the operations link).

Of course we could always put Operations back in the user menu and have the progress area on the bottom be dynamic.  
We would still want some space for a permanent status area, though....(such as line x col y in the editor)
Comment 7 Malgorzata Janczarska CLA 2012-01-24 04:57:41 EST
(In reply to comment #2)
> I also noticed the "Server Operations" link today, and it seems to get lost
> next to the privacy policy, terms of use, etc. My first guess would be this is
> a link to policy or information about server operations (scheduled downtime,
> announcements, etc). Do we even need a link to the operations list when nothing
> is running (Eclipse doesn't)? Maybe when there is nothing running the progress
> message should just be a hyperlink that says "<name of last task> completed".
> Clicking that message would take you to the complete list?

What if user hasn't yet run any operations, but he wants to check how did operations he scheduled yesterday end? What if he did git log an hour ago and we are still displaying information "Git log completed" with a link?
If we leave the operations icon in the bottom-right corner than I think it would be ok to leave the operations icon visible all the time, only grayed-out when there are no recent operations on the list and keep the operations link there.
I think it wouldn't do harm if we separate operations icon with the popup and the status message that should be somewhere on top.
Comment 8 Susan McCourt CLA 2012-01-24 11:10:05 EST
Linda and I did some work yesterday looking at the current implementation and she is mocking up an idea where progress and status could cause the toolbar to fold down when something is happening.  Semi-permanent status messages (like the editor line/col) need to find a home...I was even wondering about the line/col text serving as a command link for "goto line".  This way you would get something happening up top again, but not up in the banner, and closer to the work you were doing.  I've kind of lost track of when we use status vs. progress to report information about user stuff.  I suspect that if we separate these areas, we'll want to go change some uses of status to use progress.

If we do this, then the footer would get relatively skinny again.  At that point, I would say that "operations" could go with "settings", either in a user menu or in links at the bottom.  If at the bottom, I think we'd need to lay them out in a way that helps the user realize they are more dynamic then the other links down there.

I'm less worried about that part because it's so easy to experiment/change.  But I want to make sure we are happy with where the dynamic stuff goes.  

I expect to have new mockups by Wednesday and hopefully implemented on Thursday.
Comment 9 Simon Kaegi CLA 2012-02-12 23:11:42 EST
Moving to RC2 but might just be a verify.
Comment 10 Susan McCourt CLA 2012-02-13 11:24:53 EST
we fixed this by putting the progress bar back up under the toolbar.