From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Maximiliano Sandoval <m.sandoval@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager v2] fix #4166: restore: add resource pool selector
Date: Wed, 25 Jun 2025 16:02:26 +0200 [thread overview]
Message-ID: <0ca9a441-0f17-4c52-bbc9-9812ceae0457@proxmox.com> (raw)
In-Reply-To: <s8ozfdwx74x.fsf@proxmox.com>
Am 25.06.25 um 15:48 schrieb Maximiliano Sandoval:
> It could be placed there, however I think it makes sense to put it next
> to the storage selector (which could also be argued is an override). I
> could add a `emptyText` with value 'From backup configuration' similar
> as the storage selector though.
My conclusion would then be to move the storage to the rest of the
override settings rather than making the UX pattern even worse here...
But for one that would be certainly not the job of this patch and for
another is the storage a core parameter that is basically always
present (and often explicitly set, as one cannot see what the value
will be, a UX problem but nonetheless the status quo) whereas resource
pools are certainly more of an edge case.
Just like a hypothetical per-volume storage override–or any other
property–should also go in the "Override Setting" section.
_______________________________________________
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-06-25 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 8:23 Maximiliano Sandoval
2025-06-17 15:45 ` Thomas Lamprecht
2025-06-18 8:32 ` Fiona Ebner
2025-06-25 13:48 ` Maximiliano Sandoval
2025-06-25 14:02 ` 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=0ca9a441-0f17-4c52-bbc9-9812ceae0457@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.sandoval@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 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.