Jesse Keating wrote:
On Thursday 26 October 2006 07:14, Neal Becker wrote:
There is IMHO a _serious_ issue here. The update hangs for a
_very_ long time with no user feedback that it isn't dead. This is
on a very fast machine with lots of memory.
Believe me - there about to be a flood of complaints about this. I
can't wait to see what happens when someone with a more modest
machine tries this.
And I don't see any fix for this in any reasonable amount of time.
From a non-UI specialist: it might be a good idea to aim for a maximum
duration before updating a UI like this of 1 second. On a modern
machine, if there aint no activity for more than a second, user's are
starting to think "this is probably dead", and getting ready to hit the
reset button to fix it.
Dep resolving and transaction testing a 2000~ package update is going
to take a while. Plain and simple.
So does the process know how many packages it is going to have to
depsolve ? Perhaps some FB could come from this info ?
This would also apply to the estimated completion period during the
actual install; not showing something changing for many minutes is not
acceptable - eg 100 minutes showing for 15 minutes is strongly
suggestive that something has gone wrong. {and the shutdown dialog that
updates only every ten seconds}.
If you have some other's views on regularity of UI feedback, I'd like to
hear them.
DaveT.
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list