Mailinglist Archive: opensuse-bugs (9721 mails)
| < Previous | Next > |
[Bug 340868] Online Update Configuration GUI is poor
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Wed, 14 Nov 2007 16:15:45 -0700 (MST)
- Message-id: <20071114231545.320E0CC6B3@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=340868#c2
Marc Chamberlin <marc@xxxxxxxxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|
|marc@xxxxxxxxxxxxxxxxxx
Status|NEEDINFO |NEW
Info Provider|marc@xxxxxxxxxxxxxxxxxx |
--- Comment #2 from Marc Chamberlin <marc@xxxxxxxxxxxxxxxxxx> 2007-11-14
16:15:44 MST ---
Jiri - Please REREAD my report. I am NOT asking you to fix a problem that might
have caused a hang. I am asking you to redesign the GUI so that I, a typical
user, can make a determination as to whether progress is really being made or
whether something has hung. This GUI (as well as many others in Yast) provides
no concrete evidence that it is accomplishing the task, in this particular case
of updating my online source information. Nor does it give me a reasonable
estimate of how long such a process typically takes. When presented with these
messages and user is going to ask - How long is it reasonable to wait for the
server to be contacted? How do I know that it is doing so? How long should it
take to update the online sources? How do I as a user determine that this
update process is proceeding OK? ESPECIALLY WHEN IT IS TAKING A LONG TIME!
This GUI leaves me in the dark and gives no indication as to whether everything
is working OK or whether something has gone wrong. If one can see something
like ascii text reports being fed back showing progress, that is a good way of
indicating that progress is being made. As it stands I have no idea whether it
hung or is making progress and I just need to wait a bit longer...
Therefore I am NOT asking you to fix some problem behind the GUI, but rather
redesign and fix the GUI itself so that a user is given feedback that shows
things are working.
Marc.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Marc Chamberlin <marc@xxxxxxxxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|
|marc@xxxxxxxxxxxxxxxxxx
Status|NEEDINFO |NEW
Info Provider|marc@xxxxxxxxxxxxxxxxxx |
--- Comment #2 from Marc Chamberlin <marc@xxxxxxxxxxxxxxxxxx> 2007-11-14
16:15:44 MST ---
Jiri - Please REREAD my report. I am NOT asking you to fix a problem that might
have caused a hang. I am asking you to redesign the GUI so that I, a typical
user, can make a determination as to whether progress is really being made or
whether something has hung. This GUI (as well as many others in Yast) provides
no concrete evidence that it is accomplishing the task, in this particular case
of updating my online source information. Nor does it give me a reasonable
estimate of how long such a process typically takes. When presented with these
messages and user is going to ask - How long is it reasonable to wait for the
server to be contacted? How do I know that it is doing so? How long should it
take to update the online sources? How do I as a user determine that this
update process is proceeding OK? ESPECIALLY WHEN IT IS TAKING A LONG TIME!
This GUI leaves me in the dark and gives no indication as to whether everything
is working OK or whether something has gone wrong. If one can see something
like ascii text reports being fed back showing progress, that is a good way of
indicating that progress is being made. As it stands I have no idea whether it
hung or is making progress and I just need to wait a bit longer...
Therefore I am NOT asking you to fix some problem behind the GUI, but rather
redesign and fix the GUI itself so that a user is given feedback that shows
things are working.
Marc.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |