On 04/03/2014 04:53 AM, Hongliang Wang wrote:
Hi Adam & Aline, for current stage, I still suggest keep
other than close/dismiss.
For a reasonable user experience, I think we need 2 views: summary
Updating package 1... Finished!
Updating package 2... Finished!
Updating package 3... Finished!
Updating package 4... Finished!
Updating package 5...
For user, *progress* is the key information he/she wants. Here,
let's take a look at the 2 views:
1) With the overall progress percentage, the user can estimate a
finish time that he can switch back when the updating is done.
2) With the detailed information, the user may have the chance to
correct something, for example, after several updates, the user found
the updating always fails at 50%, so he/she open the detailed view to
find the corresponding package and take some action.
In our current back-end implementation, the user can only know the
detailed information and not obvious total progress. If we allow
close/dismiss the progress area, the user will lose everything about
I will add your idea about overall and detailed view to our backlog
On 04/02/2014 01:55 AM, Aline Manera wrote:
> On 03/14/2014 05:51 PM, Adam King wrote:
>> We'd like to be able to close/dismiss the progress area, rather than
>> just hide/show the contents.
> will you send a new patch series with Adam's suggestion?
>> On 3/13/2014 2:43 AM, Hongliang Wang wrote:
>>> Take advantage of jQuery UI to make update progress area collapsible.
>>> Signed-off-by: Hongliang Wang<hlwang(a)linux.vnet.ibm.com>
> Kimchi-devel mailing list