Project

General

Profile

Feature #3224

Upgrade Frontend Monitoring

Added by Parag Mhashilkar almost 7 years ago. Updated over 6 years ago.

Status:
New
Priority:
Low
Assignee:
Parag Mhashilkar
Category:
Frontend Monitoring
Target version:
Start date:
01/04/2013
Due date:
% Done:

0%

Estimated time:
Stakeholders:
Duration:

Description

Derek implemented the twitter style navigation scheme in #2981. Changes are in branch_v2plus_2981. Based on that we can modernize the frontend monitoring to give a consistent look and feel.

  • Changes common to all the pages
    • Apply the twitter style navigation bar to all the pages. Distribute the css preserving the copyright notice. * Remove the page heading/title completely. Highlighted menu should be enough * Put the frontend name & instance in the navigation bar below 'GlideinWMS Frontend' * Pages that have option to refresh data and last update time, bring them together since these two are related * Pages that have groups and/or link+unlink buttons: Make the link creation more intuitive like Google Maps or other web pages. This is useful to pass the url to other viewers.
  • index.html
    • Order and naming in the navigation bar and images should be consistent
  • frontendGroupGraphStatusNow.html
    • Do we want to split the page into two tabs? One for table and other for graphs?
  • frontendRRDBrowse.html, frontendRRDGroupMatrix.html, frontendStatus.html
    • Add navigation bar * Check if the groups can be moved to left side menu, just like frontendGroupGraphStatusNow.html * By default load the graph for options selected. Cons - it may slow initial access to the page * Except for frontendStatus.html, Status_Attributes is the only RRD, so we can get rid of the selection

History

#1 Updated by Parag Mhashilkar almost 7 years ago

Lets track updates in this comment since we can edit the main description

  • Changes common to all the pages
    • Apply the twitter style navigation bar to all the pages. Distribute the css preserving the copyright notice. * Remove the page heading/title completely. Highlighted menu should be enough * Put the frontend name & instance in the navigation bar below 'GlideinWMS Frontend' * Pages that have option to refresh data and last update time, bring them together since these two are related * Pages that have groups and/or link+unlink buttons: Make the link creation more intuitive like Google Maps or other web pages. This is useful to pass the url to other viewers. * Find a way to set the timezone and legend locations across all the webpages in one common place and remember the settings when the pages are revisited even after few days. Maybe use cookies or the timezone set in the browser as default (?)
  • index.html
    • Order and naming in the navigation bar and images should be consistent
  • frontendGroupGraphStatusNow.html
    • Do we want to split the page into two tabs? One for table and other for graphs?
  • frontendRRDBrowse.html, frontendRRDGroupMatrix.html, frontendStatus.html
    • Add navigation bar * Check if the groups can be moved to left side menu, just like frontendGroupGraphStatusNow.html * By default load the graph for options selected. Cons - it may slow initial access to the page * Except for frontendStatus.html, Status_Attributes is the only RRD, so we can get rid of the selection

#2 Updated by Burt Holzman almost 7 years ago

  • Assignee changed from Douglas Strain to Parag Mhashilkar

#3 Updated by Burt Holzman over 6 years ago

  • Target version changed from v3_1 to v3_x


Also available in: Atom PDF