Sorry to come in late. Jenya is on vacation so I will take the liberty
of responding on the UI design requirements.
There appears to be some confusion about "file" as demonstrated in the
Synaptic screenshot. For IPS the user's request for install/update is
for packages and so the progress feedback detail should reflect
packages. The user is not aware of the individual disk files that make
up the packages so disk file name detail feedback will not make sense.
Ideally the progress bar should update frequently and regularly so that
the user can see that things are progressing:
- one to two second update periods are desireable,
- three to four seconds are acceptable,
- five or more seconds will make users uncomfortable,
- ten or more seconds will cause the user to wonder if things are
progressing and start to wonder if they should take action.
Of course times are somewhat relative. If the update were regular every
ten seconds users would learn to be patient, but they would still feel
either uncomfortable or that the system was slow. Individuals also
different tolerances
Widely varying timed feedback should be avoided if possible. Time
variations of about 80% are not problematic while variations of more
than 300% or six seconds are to be avoided.
Frank
[EMAIL PROTECTED] wrote:
JR,
We don't want to override the internal methods at all :( If IPS can
enhance the ProgressTracker to give us what we need and adjust the
filelist.py to update ProgressTracker based on a timer for each Package
that is being downloaded and pass in the current amount of data
downloaded for the package and the amount remaining, we could remove
this duplicated code. That would be great :) Then all we have to do is
provide our own ProgressTracker implementation to consume this package
progress information. We may also choose to display the number of
downloaded and remaining files information, but not to control the per
package progress indicator.
This is good. You don't want to override these methods, and I don't
want these methods overridden. I'm still not sure I completely
understand what you need, so it would be great if you would describe in
more detail what would help you track progress. Just as an example,
it's not at all obvious to me why we need a timer in the client. I was
under the impression that the GUI would be able to run a thread in the
background that polled the download statistics at a certain interval.
It sounds like you're saying that's not sufficient.
-j
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
|
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
