From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9])
	by lore.proxmox.com (Postfix) with ESMTPS id 405BE1FF15C
	for <inbox@lore.proxmox.com>; Wed, 13 Nov 2024 11:53:36 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id 2A5B913423;
	Wed, 13 Nov 2024 11:53:37 +0100 (CET)
Message-ID: <1fea8447-3256-49b9-bf80-c5a91fbc3165@proxmox.com>
Date: Wed, 13 Nov 2024 11:53:33 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird Beta
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
 Aaron Lauterer <a.lauterer@proxmox.com>,
 Proxmox VE development discussion <pve-devel@lists.proxmox.com>
References: <20240531080703.880174-1-d.csapak@proxmox.com>
 <3725cde0-842b-4fd7-b352-e3336e1b6d20@proxmox.com>
 <1bac79ec-7598-4c8d-952f-a394044a08cb@proxmox.com>
 <c470d274-770b-4964-94de-ef97670f0694@proxmox.com>
Content-Language: en-US
From: Dominik Csapak <d.csapak@proxmox.com>
In-Reply-To: <c470d274-770b-4964-94de-ef97670f0694@proxmox.com>
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.016 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DMARC_MISSING             0.1 Missing DMARC policy
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
Subject: Re: [pve-devel] [RFC PATCH manager] api/ui: include the node ha
 status in resources call and show as icon
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>

On 11/13/24 11:49, Thomas Lamprecht wrote:
> 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.
> 

a solution that seems to improve it, would be to incread the font-size
of the wrench. It's not something we do for other icons, but
this one is especially small and bumping the font-size to e.g. 14px
(from 13) seems to make it much easier to see


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel