From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com, Shan Shaji <s.shaji@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve_flutter_frontend v3 0/2] feat #6983: add dark and tint mode support for app icon
Date: Wed, 12 Nov 2025 10:21:48 +0100 [thread overview]
Message-ID: <176293927547.1084579.14380280453596022232.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251107162543.55483-1-s.shaji@proxmox.com>
On Fri, 07 Nov 2025 17:25:41 +0100, Shan Shaji wrote:
> Previously, the home screen customization that allows users to change
> the light, dark, and tint options was not reflected in the app icon.
> This was because no dark mode variant and tint variant was added in
> the asset catalogue.
>
> To support dark mode icons, the new App Icon Composer was used to
> create icons for light, dark, and tint variants with liquid glass
> support. The app icon now adapts dynamically based on the user’s
> customization selection.
>
> [...]
Applied, thanks!
[1/2] fix #6983: ios: allow dark and tint mode icon using icon composer file
(no commit info)
[2/2] chore: ios: delete asset catalogue files in favor of icon composer file
(no commit info)
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-11-12 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 16:25 [pve-devel] " Shan Shaji
2025-11-07 16:25 ` [pve-devel] [PATCH pve_flutter_frontend v3 1/2] fix #6983: ios: allow dark and tint mode icon using icon composer file Shan Shaji
2025-11-07 16:25 ` [pve-devel] [PATCH pve_flutter_frontend v3 2/2] chore: ios: delete asset catalogue files in favor of " Shan Shaji
2025-11-12 9:21 ` Dominik Csapak [this message]
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=176293927547.1084579.14380280453596022232.b4-ty@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.shaji@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.