Project

General

Profile

Feature #6677

Dynamically update component pages

Added by Evgeny Novikov over 4 years ago. Updated over 4 years ago.

Status:
New
Priority:
High
Category:
Bridge
Target version:
-
Start date:
02/01/2016
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

At the moment just the job page is automatically updated but this is useful for component pages as well.


Related issues

Blocked by Klever - Bug #6715: Automatic update of page is incompleteClosed02/02/2016

Actions

History

#1

Updated by Vladimir Gratinskiy over 4 years ago

Updates are good for static values. But whole page structure depends on our values both on job and reports pages. Now job's parent, job's name, files and so on are not updated on job's page. I still don't think "autoupdate" is a good idea for job's page. And I don't think it will be good for reports' pages as well.

#2

Updated by Evgeny Novikov over 4 years ago

As I realize the main problem with implementation of this feature is just it is quite labour and error-prone to detect dynamic parts of pages and to implement their automatic updates.

But the feature is very useful. For instance, after implementation of #6889 some component specific data is periodically updated on the corresponding component pages. Besides it can be useful to see updates of consumed resources, of underlying safes, unsafes, unknowns and associated marks.

I can suppose an intermediate solution in this case: just update the whole pages periodically if users enable this by hand like at http://vcloud.sosy-lab.org/cpachecker/webclient/master/info. I guess that corresponding option should be very temporary, it should be set on a particular page and should be forgotten when a user leaves that page. Besides it would be great to have an ability to specify an update interval, say, each 1, 2, 3, 4, 5 seconds like for playing error traces.

#3

Updated by Evgeny Novikov over 4 years ago

  • Priority changed from Normal to High

I consider this very useful and not so hard to implement in case of the suggested intermediate solution.

#4

Updated by Alexey Khoroshilov over 4 years ago

Evgeny Novikov wrote:

I can suppose an intermediate solution in this case: just update the whole pages periodically

I would say it is very user unfriendly solution.
Is the framework not well suitable for autorefreshing of page elements?
https://stackoverflow.com/questions/28015865/django-ajax-jquery-refreshing-div-elements-on-timer

#5

Updated by Evgeny Novikov over 4 years ago

Alexey Khoroshilov wrote:

Evgeny Novikov wrote:

I can suppose an intermediate solution in this case: just update the whole pages periodically

I would say it is very user unfriendly solution.

I agree that in general case this is of course ugly. But as for component pages it fits quite well current requirements:

  • In the most of cases the users are glad to get static component pages and leave them or move through some link.
  • Sometimes, e.g. when a component page has a dynamically updated component specific data (e.g. validation results), it is enough to update the whole page automatically as we do by pressing F5 manually. Usually we are just interested in static but fresh picture of data reports without any interaction. When we will need the latter we will need to switch off automatic updates.

Is the framework not well suitable for autorefreshing of page elements?
https://stackoverflow.com/questions/28015865/django-ajax-jquery-refreshing-div-elements-on-timer

I guess that Vladimir either already uses some framework like this one or developed its own one. Anyway it works quite fair for the job page, but it requires too much time to detect and fix all related issues.

That's why I suppose to implement simple and generic automatic updating of whole pages and implement something more useful and elegant just when we will do need this.

Also available in: Atom PDF