<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 04/03/2014 04:53 AM, Hongliang Wang
wrote:<br>
</div>
<blockquote cite="mid:533D1379.8080307@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Hi Adam & Aline, for current stage, I still suggest keep
hide/show other than close/dismiss.<br>
<br>
For a reasonable user experience, I think we need 2 views:
summary and detailed.<br>
<br>
<b>Summary View:</b><br>
=======================<br>
Updating software...<br>
____________________<br>
<u>|50%</u><u> </u>|<br>
<br>
▶ Details<br>
=======================<br>
<br>
<b>Detailed View:</b><br>
=======================<br>
Updating software...<br>
____________________<br>
<u>|50%</u><u> </u>|<br>
<br>
▼ Details<br>
Updating package 1... Finished!<br>
Updating package 2... Finished!<br>
Updating package 3... Finished!<br>
Updating package 4... Finished!<br>
Updating package 5... <br>
=======================<br>
<br>
For user, <b>progress</b> is the key information he/she
wants. Here, let's take a look at the 2 views:<br>
1) With the overall progress percentage, the user can estimate
a finish time that he can switch back when the updating is done.<br>
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.<br>
<br>
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 the progress.<br>
</blockquote>
<br>
Ok.<br>
I will add your idea about overall and detailed view to our backlog<br>
<br>
<blockquote cite="mid:533D1379.8080307@linux.vnet.ibm.com"
type="cite"> <br>
<div class="moz-cite-prefix">On 04/02/2014 01:55 AM, Aline Manera
wrote:<br>
</div>
<blockquote cite="mid:533AFDA7.8060203@linux.vnet.ibm.com"
type="cite">On 03/14/2014 05:51 PM, Adam King wrote: <br>
<blockquote type="cite">We'd like to be able to close/dismiss
the progress area, rather than just hide/show the contents. <br>
</blockquote>
<br>
Hongliang, <br>
<br>
will you send a new patch series with Adam's suggestion? <br>
<br>
<blockquote type="cite"> <br>
On 3/13/2014 2:43 AM, Hongliang Wang wrote: <br>
<blockquote type="cite">Take advantage of jQuery UI to make
update progress area collapsible. <br>
<br>
Signed-off-by: Hongliang Wang<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:hlwang@linux.vnet.ibm.com"><hlwang@linux.vnet.ibm.com></a>
<br>
</blockquote>
<br>
</blockquote>
<br>
_______________________________________________ <br>
Kimchi-devel mailing list <br>
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>