Re: [pve-devel] [PATCH pve-manager v3 1/1] ui: fix #6209: create snapshots and backups from context menu

[Thomas Lamprecht <t.lamprecht@proxmox.com>]

Am 07.10.25 um 10:42 schrieb Shannon Sterz:
> one small thought: have you explored whether querying the features of
> the guest when opening the context menu and graying out the snapshot
> option is viable? imo that would be a nicer user experience, but the
> overhead of querying the backend there might be too much.

FWIW, Nicolas did that in v1/v2, but I wondered w.r.t. slow backend
or spotty and/or high-latency connection making this odd to use.
But I just found that my reply was not CC'ing the list, so I just
re-send it for the record:
https://lore.proxmox.com/pve-devel/9563cc43-f8ad-4b33-b8ea-a22d22b3405e@proxmox.com/

That said, given that you suggested the other way around for UX, it
might be indeed better to keep it that way, or at least actually try
how that way works with a slow backend (developer tools can simulate
slow network (the chromium based ones are a bit more powerful in that
regard IIRC), or alternatively use a traffic control (tc) netem qdisc
that adds latency [0] can be added on the PVE server.
Because as mentioned, it could be fine your previous way and the one
Shannon also would prefer, I rather wanted to avoid that we just take
our rather perfect fast and sub-milliseconds lab environments as sole
base for UX decisions.

[0]: https://manpages.debian.org/trixie/iproute2/tc-netem.8.en.html
     e.g. something like: tc qdisc add dev eth0 root netem delay 3000ms


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel