From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH manager 0/5] tags ui follow up patches
Date: Thu, 17 Nov 2022 18:22:54 +0100 [thread overview]
Message-ID: <9eb8b6c8-1b00-a88f-beb6-b2a2391d0fc8@proxmox.com> (raw)
In-Reply-To: <20221117145623.661109-1-d.csapak@proxmox.com>
Am 17/11/2022 um 15:56 schrieb Dominik Csapak:
> overall ui improvements of the tags ui, see the individual patches
> for details
>
> intended as follow up to my v11 tags ui series
>
> Dominik Csapak (5):
> ui: rework inline tag editing
> ui: tags: make sorting more natural
> ui: tags: hide already set tags in dropdown
> ui: change style of ListField
> ui: tags: add preview to tag shape option
>
> www/css/ext6-pve.css | 28 ++---
> www/manager6/Utils.js | 8 +-
> www/manager6/dc/OptionView.js | 37 ++++++-
> www/manager6/dc/RegisteredTagsEdit.js | 6 +-
> www/manager6/dc/UserTagAccessEdit.js | 6 +-
> www/manager6/form/ListField.js | 86 +++++++++------
> www/manager6/form/Tag.js | 118 ++++++++++-----------
> www/manager6/form/TagEdit.js | 144 ++++++++++++++------------
> 8 files changed, 240 insertions(+), 193 deletions(-)
>
applied series, thanks!
prev parent reply other threads:[~2022-11-17 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 14:56 [pve-devel] " Dominik Csapak
2022-11-17 14:56 ` [pve-devel] [PATCH manager 1/5] ui: rework inline tag editing Dominik Csapak
2022-11-17 14:56 ` [pve-devel] [PATCH manager 2/5] ui: tags: make sorting more natural Dominik Csapak
2022-11-17 14:56 ` [pve-devel] [PATCH manager 3/5] ui: tags: hide already set tags in dropdown Dominik Csapak
2022-11-17 14:56 ` [pve-devel] [PATCH manager 4/5] ui: change style of ListField Dominik Csapak
2022-11-17 14:56 ` [pve-devel] [PATCH manager 5/5] ui: tags: add preview to tag shape option Dominik Csapak
2022-11-17 17:22 ` 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=9eb8b6c8-1b00-a88f-beb6-b2a2391d0fc8@proxmox.com \
--to=t.lamprecht@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