From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 2/3] ceph: ui: followup: change blue for PGs in working state
Date: Fri, 21 Jul 2023 15:06:25 +0200 [thread overview]
Message-ID: <20230721130626.4018339-2-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20230721130626.4018339-1-a.lauterer@proxmox.com>
The previous light blue was hard to see in the light theme, especially
if it only had a narrow slice in the cake diagram.
This darker blue is easily visilbe and distinguishable in the light and
dark theme.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
These patches are all a follow up to Alexandre's. This one in
widget-toolkit is needed to specify the css color specifically.
www/manager6/ceph/StatusDetail.js | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/www/manager6/ceph/StatusDetail.js b/www/manager6/ceph/StatusDetail.js
index e1bf425a..7198ba62 100644
--- a/www/manager6/ceph/StatusDetail.js
+++ b/www/manager6/ceph/StatusDetail.js
@@ -94,7 +94,7 @@ Ext.define('PVE.ceph.StatusDetail', {
colors: [
'#CFCFCF',
'#21BF4B',
- '#C2DDF2',
+ '#3892D4',
'#FFCC00',
'#FF6C59',
],
@@ -194,7 +194,7 @@ Ext.define('PVE.ceph.StatusDetail', {
},
{
text: gettext('Working'),
- cls: 'normal',
+ cls: 'working',
},
{
text: gettext('Warning'),
--
2.39.2
next prev parent reply other threads:[~2023-07-21 13:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 10:54 [pve-devel] [PATCH pve-manager] ui: ceph status: add pg warning state Alexandre Derumier
2023-06-22 13:50 ` Aaron Lauterer
2023-07-21 13:06 ` [pve-devel] [PATCH widget-toolkit 1/3] css: add 'working' css color class Aaron Lauterer
2023-07-21 13:06 ` Aaron Lauterer [this message]
2023-07-21 13:06 ` [pve-devel] [PATCH manager 3/3] ceph: ui: rename PG state error to critical Aaron Lauterer
2023-07-21 13:08 ` [pve-devel] [PATCH pve-manager] ui: ceph status: add pg warning state Aaron Lauterer
2023-08-07 7:46 ` DERUMIER, Alexandre
2023-08-08 7:32 ` Aaron Lauterer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230721130626.4018339-2-a.lauterer@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox