From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Aaron Lauterer <a.lauterer@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH pve_flutter_frontend v3 0/3] Add first welcome screen
Date: Sun, 14 Mar 2021 18:49:47 +0100 [thread overview]
Message-ID: <6b2e262c-c69a-b940-6f30-4f0a2d695e87@proxmox.com> (raw)
In-Reply-To: <20201211103708.32431-1-a.lauterer@proxmox.com>
On 11.12.20 11:37, Aaron Lauterer wrote:
> This patch series introduces a "first welcome screen" shown on first
> start.
>
> Additionally, a class that stores the proxmox corporate identity (CI)
> colors is introduced.
>
> Changes from v2:
> Worked on the overall layout of the welcome screen to look good on
> screens on all sizes. Limited the max width and made sure that on really
> small screens or in landscape mode, scrolling is possible.
>
> Made sure the logo on the first page does not get too big when in
> landscape mode.
>
>
> Changes to v1:
> * rework welcome screens, mainly use buttons instead of text links
> * cleanup code
> * use async where needed
> * fix image sizes for added logo
>
> Aaron Lauterer (3):
> add class for Proxmox corporate identity colors
> add Proxmox symbol logo white orange
> Add first welcome screen
>
applied series, thanks!
prev parent reply other threads:[~2021-03-14 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 10:37 [pve-devel] " Aaron Lauterer
2020-12-11 10:37 ` [pve-devel] [PATCH pve_flutter_frontend v3 1/3] add class for Proxmox corporate identity colors Aaron Lauterer
2020-12-11 10:37 ` [pve-devel] [PATCH pve_flutter_frontend v3 2/3] add Proxmox symbol logo white orange Aaron Lauterer
2020-12-11 10:37 ` [pve-devel] [PATCH pve_flutter_frontend v3 3/3] Add first welcome screen Aaron Lauterer
2021-03-14 17:49 ` Thomas Lamprecht [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=6b2e262c-c69a-b940-6f30-4f0a2d695e87@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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