Bug 617586
| Summary: | Implement progress dialog for long-running operations | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Andrew Beekhof <abeekhof> |
| Component: | luci | Assignee: | Ryan McCabe <rmccabe> |
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.0 | CC: | bbrock, cluster-maint, fdinitto, rmusil, ssaha |
| Target Milestone: | rc | Keywords: | RHELNAK |
| Target Release: | 6.1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | luci-0.23.0-12.el6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-05-19 13:56:10 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 617587 | ||
|
Description
Andrew Beekhof
2010-07-23 13:41:43 UTC
This issue has been proposed when we are only considering blocker issues in the current Red Hat Enterprise Linux release. ** If you would still like this issue considered for the current release, ask your support representative to file as a blocker on your behalf. Otherwise ask that it be considered for the next Red Hat Enterprise Linux release. ** Not sure that this makes sense to do if the user can just hit the refresh button at the top of the screen. We'll need to talk to the design people and see what they feel would be best. Bumping to 6.1 since this isn't critical for 6.0. Looking from both user and programmer perspective, I can imagine that: 1) for each action that requires refresh the most suitable (let's say typical+reserve time) period is found 2) using JavaScript, after the page is loaded, the timer is set to this value and then visually counted down and when it reaches 0, it will trigger page reload automatically 3) near this visual counter, there will be also link-like (somehow highlighted to notify user it can be clicked) label "refresh immediately" or something like this For this purpose, flash2 component could be extended for this kind of messages. More challenging idea would be to keep displaying "busy message" until the underlying code really finished what expected. But this sounds like overkill, maybe even impossible with existing design. (In reply to comment #5) The previous applies e.g. to creating cluster (mentioned in bug description), which really wants user to reload the page on its own to continue. Contrary, there are situations where page reload only serves to remove "message box". The example of this can be node addition (also mentioned in bug description), after which the fully working GUI is shown. It is true that very visible place within this GUI is covered with the message box informing about such action (node adition) and that this panel can be annoying once it is read, but this could be easily addressed with a "hide" button placed inside this panel that would be able to remove the whole message box (-> no need to reload the page to get rid of that box). There are currently two ways to achieve the above (see [1], section "basic UI components"): 1. using WebFlash component integrated to TurboGears2 2. using flash2 component which is own work and thus more flexible (in term of customization) An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0655.html |