From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Markus Frank <m.frank@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager v17 10/10] ui: add options to add virtio-fs to qemu config
Date: Tue, 8 Apr 2025 00:42:59 +0200 [thread overview]
Message-ID: <06a8615c-16f0-4662-9a73-73e701e0be81@proxmox.com> (raw)
In-Reply-To: <20250407134950.265270-11-m.frank@proxmox.com>
Am 07.04.25 um 15:49 schrieb Markus Frank:
> + {
> + xtype: 'displayfield',
> + userCls: 'pmx-hint',
> + value: gettext('Directory Mappings can be managed under Datacenter -> Directory Mappings'),
> + },
Hints can be OK, but in the end they are always some form of
admission of bad UX, as said often OK as they at least slightly
improve the status quo, not everything can be perfected. But, if
they can be replaced by some actionable feature, then doing so is
always better.
Here we e.g. could replace the hint with showing a simple
"Goto <directory mapping management>" below the field that is a link
to the respective datacenter option tab.
@Dominik: didn't we have a function or use-site of something like
this already? I had the StateProvider in mind, but nothing very
obvious (albeit it would have the info required to assemble the link
I guess).
_______________________________________________
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-04-07 22:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 13:49 [pve-devel] [PATCH docs/qemu-server/manager v17 0/10] Virtio-fs Markus Frank
2025-04-07 13:49 ` [pve-devel] [PATCH docs v17 1/10] add doc section for the shared filesystem virtio-fs Markus Frank
2025-04-07 13:49 ` [pve-devel] [PATCH qemu-server v17 2/10] d/control: add virtiofsd to Recommends for qemu-server Markus Frank
2025-04-07 13:49 ` [pve-devel] [PATCH qemu-server v17 3/10] fix #1027: virtio-fs support Markus Frank
2025-04-07 13:49 ` [pve-devel] [PATCH qemu-server v17 4/10] migration: check_local_resources for virtiofs Markus Frank
2025-04-07 13:49 ` [pve-devel] [PATCH qemu-server v17 5/10] disable snapshot (with RAM) and hibernate with virtio-fs devices Markus Frank
2025-04-07 13:49 ` [pve-devel] [PATCH manager v17 06/10] api: add resource map api endpoints for directories Markus Frank
2025-04-07 13:49 ` [pve-devel] [PATCH manager v17 07/10] ui: add edit window for dir mappings Markus Frank
2025-04-07 13:49 ` [pve-devel] [PATCH manager v17 08/10] ui: add resource mapping view for directories Markus Frank
2025-04-07 13:49 ` [pve-devel] [PATCH manager v17 09/10] ui: form: add selector for directory mappings Markus Frank
2025-04-07 13:49 ` [pve-devel] [PATCH manager v17 10/10] ui: add options to add virtio-fs to qemu config Markus Frank
2025-04-07 22:42 ` Thomas Lamprecht [this message]
2025-04-08 6:54 ` Dominik Csapak
2025-04-07 14:31 ` [pve-devel] [PATCH docs/qemu-server/manager v17 0/10] Virtio-fs Filip Schauer
2025-04-07 22:52 ` 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=06a8615c-16f0-4662-9a73-73e701e0be81@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.frank@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal