From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager 3/3] ui: wizards: allow adding tags in the qemu/lxc create wizard
Date: Tue, 24 Oct 2023 16:48:34 +0200 [thread overview]
Message-ID: <261471e2-5423-4aeb-a0cf-9891a2b2a154@proxmox.com> (raw)
In-Reply-To: <20231019133607.1416999-3-d.csapak@proxmox.com>
Am 19/10/2023 um 15:36 schrieb Dominik Csapak:
> in the general tab in the advanced section.
>
> For that to work, we introduce a new option for the TagEditContainer
> named 'editOnly', which controls now the cancel/finish buttons,
> automatically enter edit mode and disable enter/escape keypresses.
>
> We also prevent now the loading of tags while in edit mode, so the tags
> don't change while editing (this can be jarring and unexpected).
>
> In the wizard, we override the layout such that the tags wrap when there
> are too many, and make the field scrollable and set a height, so that
> the user can enter as many tags as he wants without having the field
> overflow or cut off.
>
> To properly align the input with the '+' button, we have to add a custom
> css class there. (In the hbox we could set the alignment, but this is
> not possible in the 'column' layout)
>
I'd wrap this in a fieldset with Tags as legend (well, still "title" in
ExtJS), ideally in its own small PVE.form.TagEditFieldSet module, that
extends the Ext.form.FieldSet class? That could then also contain
the getValue handling, further reducing the wizard specific changes.
Allowing the height to grow until a max-height (i.e., fills out wizard
panel) and only then get scrollable would be still nice though.
next prev parent reply other threads:[~2023-10-24 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 13:36 [pve-devel] [PATCH manager 1/3] ui: tags: fix focus for edit mode Dominik Csapak
2023-10-19 13:36 ` [pve-devel] [PATCH manager 2/3] ui: tags: prevent pasting non plain-text content Dominik Csapak
2023-10-19 13:59 ` Dominik Csapak
2023-10-24 9:53 ` Thomas Lamprecht
2023-10-24 9:57 ` Dominik Csapak
2023-10-24 10:07 ` Thomas Lamprecht
2023-10-24 10:51 ` Dominik Csapak
2023-10-24 10:52 ` Thomas Lamprecht
2023-10-19 13:36 ` [pve-devel] [PATCH manager 3/3] ui: wizards: allow adding tags in the qemu/lxc create wizard Dominik Csapak
2023-10-24 14:48 ` Thomas Lamprecht [this message]
2023-10-24 14:49 ` [pve-devel] applied: [PATCH manager 1/3] ui: tags: fix focus for edit mode Thomas Lamprecht
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=261471e2-5423-4aeb-a0cf-9891a2b2a154@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