Bug 344047 - [client] progress service OK status could be improved
Summary: [client] progress service OK status could be improved
Status: RESOLVED FIXED
Alias: None
Product: Orion (Archived)
Classification: ECD
Component: Client (show other bugs)
Version: 0.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 0.5   Edit
Assignee: Susan McCourt CLA
QA Contact:
URL:
Whiteboard:
Keywords: polish
Depends on: 371261
Blocks:
  Show dependency tree
 
Reported: 2011-04-27 17:04 EDT by Susan McCourt CLA
Modified: 2012-10-04 10:52 EDT (History)
3 users (show)

See Also:


Attachments
screenshot (52.94 KB, image/png)
2011-04-27 17:04 EDT, Susan McCourt CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Susan McCourt CLA 2011-04-27 17:04:41 EDT
Created attachment 194214 [details]
screenshot

after a successful merge in git, the progress message says "OK"

It would be cool if the progress service could special case the "OK" message and say something a little better.  I think a good solution might be to add a parameter to showWhile

showWhile: function(deferred, message, taskName)

And we could post info like

taskName + " is complete."

In fact, this would be even more useful for the case where a showWhile doesn't provide a final message or status.  Having the progress message disappear may not be enough for the user, it would be nicer to have a completion message.

The taskName could also then be used for cases where more than one thing is going on, for showing progress from multiple tasks, etc.
Comment 1 Susan McCourt CLA 2011-06-13 16:51:16 EDT
We have many implementation-oriented status messages, and I don't see that OK warrants at special case at this time.  I'd rather add the "taskName" notion in a later release, do some animation, etc. and then consider the OK special case.
Comment 2 Susan McCourt CLA 2012-02-23 14:06:34 EST
Things have changed with progress (we have animation now, etc.) but the basic point is still relevant:

When something is "OK" do we need more context, like saying what was OK?  This is especially relevant if we decide to keep a history.  A bunch of "OK"s are kind of useless.
Comment 3 Susan McCourt CLA 2012-05-18 15:29:56 EDT
moving out of 0.5M2 to 0.5 milestone until we have more specific buckets for future
Comment 4 Susan McCourt CLA 2012-10-04 10:52:03 EDT
I haven't seen "OK" in a long time.