From: Lukas Wagner <l.wagner@proxmox.com>
To: pbs-devel@lists.proxmox.com, pve-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH manager v2 1/2] ui: replace Proxmox logo with SVG version
Date: Mon, 4 Aug 2025 11:02:27 +0200 [thread overview]
Message-ID: <20250804090228.192088-4-l.wagner@proxmox.com> (raw)
In-Reply-To: <20250804090228.192088-1-l.wagner@proxmox.com>
The old PNG was quite small and looked blurry when using >100% scaling.
Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
---
www/manager6/Workspace.js | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/www/manager6/Workspace.js b/www/manager6/Workspace.js
index c4bbfccc..03628b5a 100644
--- a/www/manager6/Workspace.js
+++ b/www/manager6/Workspace.js
@@ -343,7 +343,8 @@ Ext.define('PVE.StdWorkspace', {
margin: '2 0 2 5',
items: [
{
- xtype: 'proxmoxlogo',
+ xtype: 'proxmoxLogoSvg',
+ prefix: 'pwt',
},
{
minWidth: 150,
--
2.47.2
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
WARNING: multiple messages have this Message-ID
From: Lukas Wagner <l.wagner@proxmox.com>
To: pbs-devel@lists.proxmox.com, pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager v2 1/2] ui: replace Proxmox logo with SVG version
Date: Mon, 4 Aug 2025 11:02:27 +0200 [thread overview]
Message-ID: <20250804090228.192088-4-l.wagner@proxmox.com> (raw)
In-Reply-To: <20250804090228.192088-1-l.wagner@proxmox.com>
The old PNG was quite small and looked blurry when using >100% scaling.
Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
---
www/manager6/Workspace.js | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/www/manager6/Workspace.js b/www/manager6/Workspace.js
index c4bbfccc..03628b5a 100644
--- a/www/manager6/Workspace.js
+++ b/www/manager6/Workspace.js
@@ -343,7 +343,8 @@ Ext.define('PVE.StdWorkspace', {
margin: '2 0 2 5',
items: [
{
- xtype: 'proxmoxlogo',
+ xtype: 'proxmoxLogoSvg',
+ prefix: 'pwt',
},
{
minWidth: 150,
--
2.47.2
_______________________________________________
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:[~2025-08-04 9:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 9:02 [pbs-devel] [PATCH manager/proxmox{-widget-toolkit, -backup} v2 0/4] " Lukas Wagner
2025-08-04 9:02 ` [pve-devel] " Lukas Wagner
2025-08-04 9:02 ` [pbs-devel] [PATCH proxmox-widget-toolkit v2 1/1] add Proxmox logo as SVG Lukas Wagner
2025-08-04 9:02 ` [pve-devel] " Lukas Wagner
2025-08-04 9:02 ` [pve-devel] [PATCH proxmox-backup v2 1/1] ui: replace Proxmox logo with SVG version Lukas Wagner
2025-08-04 9:02 ` [pbs-devel] " Lukas Wagner
2025-08-04 9:02 ` Lukas Wagner [this message]
2025-08-04 9:02 ` [pve-devel] [PATCH manager v2 1/2] " Lukas Wagner
2025-08-04 9:02 ` [pve-devel] [PATCH manager v2 2/2] ui: add 5px of padding between Proxmox logo and product name Lukas Wagner
2025-08-04 9:02 ` [pbs-devel] " Lukas Wagner
2025-08-04 9:27 ` [pbs-devel] [PATCH manager/proxmox{-widget-toolkit, -backup} v2 0/4] replace Proxmox logo with SVG version Christian Ebner
2025-08-04 9:27 ` [pve-devel] " Christian Ebner
2025-08-04 9:31 ` [pbs-devel] [pve-devel] " Lukas Wagner
2025-08-04 9:31 ` [pve-devel] [pbs-devel] " Lukas Wagner
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=20250804090228.192088-4-l.wagner@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=pbs-devel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.