From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH manager v2 3/3] ui: qemu hardware view: split out disks and nics into grids
Date: Tue, 12 May 2026 04:06:35 +0200 [thread overview]
Message-ID: <c8d4be05-6977-4171-95b3-31d0fc4022d8@proxmox.com> (raw)
In-Reply-To: <20260508134110.4001168-4-d.csapak@proxmox.com>
On 08/05/2026 15:39, Dominik Csapak wrote:
> This is done to improve visibility of configuration of disks and nics.
> Currently only the raw property string is shown in the UI, which leads
> to bad UX when having many options configured and especially when having
> pending changes in these situations because it's hard to parse visually.
>
> The disks and nics are shown below the main options, each as their own
> grids with relevant columns. By default all columns that can be edited
> in the gui are shown (with the exception of the bandwidth limits, since
> they're not often used and blow up the number of columns). All other
> options from the config are there but hidden by default.
>
> As a fallback, in case there are new options not yet in the ui, a 'Raw
> Config' column was added, which contains the raw property string again
> (but it's hidden by default).
>
> Some notes on the implementation:
>
> The stores for the new grids are populated on each load of the main
> grid, and the we have one combined pending store that's just there to
> save the parsed pending values.
>
> To keep the diff smaller, some helpers are introduced to forward some
> methods to the main hardware grid.
>
> The selection change introduces some logic to keep the selection only
> in one grid, so there can be no conflict on the selected values.
Thanks for this, main question here: why not move the buttons too?
I.e., the hardware view is rather crowded and that's a main reason
for doing this originally, but a big part of the problem isn't really
the amount of rows (for VMs with many disks and or NICs that naturally
can become a problem too), but the edit buttons and their complex
state/display changes depending on what is selected.
In my (not so thought out!) vision I'd have added a tbar to each
panel and reworked the buttons such that only the ones relevant for the
elemens in there are shown, as else this is IMO going sidewards, if not
even getting slightly worse in some aspects, as the element to edit and
the edit/action button are even a "bigger" distance between them, so to
say.
Also, might be nice to have some explicit rationale for why things like
TPM and EFI and maybe even SCSI controller are not part of the disks
panel - not saying the must be, but they are at least hard disk related
and thus IMO worth adding an explicit rationale, even if they are not
normal hard disks and thus fall out a narrow/literal interpretation
of the "Hard Disks" sub-panel.
Layout wise I'm also not so sure if it wouldn't be better to split
the vertical space more evenly (or give the general one a only som
padding and flex the other two below?).
next prev parent reply other threads:[~2026-05-12 2:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 13:38 [PATCH manager v2 0/3] ui: split out disks and nics into grids Dominik Csapak
2026-05-08 13:38 ` [PATCH manager v2 1/3] ui: utils: factor out 'media=cdrom' check Dominik Csapak
2026-05-08 13:38 ` [PATCH manager v2 2/3] ui: factor out the guest key nic regex check Dominik Csapak
2026-05-08 13:38 ` [PATCH manager v2 3/3] ui: qemu hardware view: split out disks and nics into grids Dominik Csapak
2026-05-12 2:06 ` Thomas Lamprecht [this message]
2026-05-12 7:12 ` Dominik Csapak
2026-05-15 9:21 ` superseded: [PATCH manager v2 0/3] ui: " Dominik Csapak
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=c8d4be05-6977-4171-95b3-31d0fc4022d8@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 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.