Ticket #8325 (new defect)

Opened 6 years ago

Last modified 5 years ago

Software update should ends with an "OK" button, not a "Refresh" button.

Reported by: ohshima Owned by: cscott
Priority: normal Milestone: 9.1.0-cancelled
Component: sugar Version: not specified
Keywords: cjbfor9.1.0 Cc:
Action Needed: never set Verified: no
Deployments affected: Blocked By:
Blocking:

Description

When you perform Software update, it finishes a message "Your software is up-to-date." and a big button for refresh. Naturally, the user press the button right there but it will just repeat the update checking that is just done seconds ago. It is bad especially when you are operating on a laptop whose language setting is not something you understand!

The Refresh button should be replaced with a big "OK" button that takes you back to the panel.

Change History

Changed 6 years ago by gregorio

  • milestone changed from Not Triaged to 8.2.1

Changed 6 years ago by gregorio

  • owner changed from marco to cscott

Hi Ohshima,

Very good suggestion!

I marked it for possible resolution in 8.2.1 as its a little too late to get in to 8.2.

Thanks,

Greg S

Changed 6 years ago by cscott

  • owner changed from cscott to Eben

Reassigning to Eben.

None of the control panels have an 'OK' button; they all use the checkbox in the top corner instead.

I'll let Eben decide how/if he wants to update the UI.

Changed 6 years ago by Eben

I don't think we should complicate matters by creating multiple ways to leave a given module; retaining the buttons in the toolbar for exiting is strongly preferred. Perhaps we could change the text on the button to "check again" or something else more explicit, but as you mention that doesn't much help someone who doesn't read (or read the language presented). Is there a way to make the icon clearer?

Changed 6 years ago by ohshima

The button in question doesn't have to "leave the module". Just going back to the "panel" with language, about, and software update would be the prefered action. Why do you want to "check again" right after a check is done?

Changed 6 years ago by cscott

Because the first check might have had network problems, or have been done days ago, or I might be a developer and I just uploaded a new version?

Changed 6 years ago by cscott

I could probably be convinced that we should just remove the 'refresh' button in the 'everything went okay' case and only show if it there was some (network or other) problem.

Changed 6 years ago by ohshima

Replying to cscott:

Because the first check might have had network problems, or have been done days ago, or I might be a developer and I just uploaded a new version?

Well, I'm talking about the situation when the update is just finished. Wanting to do the check right away is not the common case, so making it default doesn't make much sense.

I could probably be convinced that we should just remove the 'refresh' button in the 'everything went okay' case and only show if it there was some (network or other) problem.

It would be better.

Changed 6 years ago by Eben

Yeah, that makes sense to me.

Changed 6 years ago by cscott

  • owner changed from Eben to cscott

Changed 5 years ago by mstone-xmlrpc

  • keywords cjbfor9.1.0 added
  • milestone changed from 8.2.1 to 9.1.0

Pushing out to 9.1.0, per edmcnierney's request.

Changed 5 years ago by cscott

Fixed in git.

Changed 5 years ago by cscott

Should be in sugar-update-control 0.20 when it is released.

Note: See TracTickets for help on using tickets.