From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Aaron Lauterer <a.lauterer@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pve-devel] [RFC PATCH manager] api/ui: include the node ha status in resources call and show as icon
Date: Wed, 13 Nov 2024 11:49:33 +0100 [thread overview]
Message-ID: <c470d274-770b-4964-94de-ef97670f0694@proxmox.com> (raw)
In-Reply-To: <1bac79ec-7598-4c8d-952f-a394044a08cb@proxmox.com>
Am 13.11.24 um 10:16 schrieb Aaron Lauterer:
> We use #3892d4 for the Ceph PG pie chart if PGs are doing some non
> critical work. It is a "mid" blue that works quite well in both, light
> and dark theme.
That or no specific color at all would work for me.
> The wrench symbol can be a bit thin as it is even smaller than the main
> icon. Maybe the `cog` icon works better? But no hard feelings on either
> from my side.
One option would be to use the same thing as we do for PBS Datastore
maintenance, is kinda related. There we just grey out the datastore icon
and use a wrench with "normal" foreground color, albeit it might make it
harder do differ between shutdown and powered on nodes.
A cog is more for options/settings, not so much for maintenance IMO.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-11-13 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 8:07 Dominik Csapak
2024-05-31 10:07 ` Dominik Csapak
2024-11-12 19:49 ` Thomas Lamprecht
2024-11-13 9:16 ` Aaron Lauterer
2024-11-13 10:49 ` Thomas Lamprecht [this message]
2024-11-13 10:53 ` Dominik Csapak
2024-11-13 11:20 ` Thomas Lamprecht
2024-11-13 11:39 ` Dominik Csapak
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=c470d274-770b-4964-94de-ef97670f0694@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=a.lauterer@proxmox.com \
--cc=d.csapak@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