From: "Daniel Kral" <d.kral@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Cc: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH widget-toolkit v2 1/1] window: add ConfirmRemoveDialog
Date: Fri, 26 Sep 2025 16:15:13 +0200 [thread overview]
Message-ID: <DD2SMVLCEPE2.4MHT70UA7R9X@proxmox.com> (raw)
In-Reply-To: <20250924160747.430018-6-m.koeppl@proxmox.com>
On Wed Sep 24, 2025 at 6:07 PM CEST, Michael Köppl wrote:
> This dialog window can be used to create confirmation dialogs with some
> amount of customization. It allows adding additional items, optionally
> supports confirming intent by entering the ID of the affected guest,
> storage, or resource, customizing the buttons of the dialog.
>
> It is heavily based on the SafeDestroy window, but makes it more
> general-purpose, covering both Yes/No dialogs as well as the safe
> destroy dialogs with confirmation.
>
> Signed-off-by: Michael Köppl <m.koeppl@proxmox.com>
> ---
> I settled on adding this window because Ext.Msg.MessageBox is not really
> made to be extended, so I chose a similar approach to what was done for
> SafeDestroy, extending Ext.window.Window instead. I borrowed heavily
> from SafeDestroy, but made the component a bit more
> general-purpose/flexible. This component can now be used for yes/no
> dialog windows as well as the safe destroy dialogs for guests/storages,
> etc.
>
> I'll also send follow-up patches that use ConfirmRemoveDialog for the
> SafeDestroyGuest and SafeDestroyStorage windows in pve-manager.
I think it's a good idea to combine these, but at the same time it's a
bit hard to review not seeing the diff from Proxmox.window.SafeDestroy
here directly..
I diffed them locally and if it's not too much work, it might be nice to
adapt Proxmox.window.SafeDestroy and set dangerous = true there by
default and only set dangerous = false for the special case in
ConfirmRemoveResource / SafeDestroyResource, but that might also be just
nit-picking from my side.
What do you think?
_______________________________________________
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-09-26 14:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 16:07 [pve-devel] [PATCH container/docs/ha-manager/manager/proxmox-widget-toolkit/qemu-server v2 0/8] fix #6613: update HA rules upon resource deletion Michael Köppl
2025-09-24 16:07 ` [pve-devel] [PATCH ha-manager v2 1/2] fix #6613: update rules containing the resource to be deleted Michael Köppl
2025-09-24 16:07 ` [pve-devel] [PATCH ha-manager v2 2/2] api: add purge parameter for resource deletion Michael Köppl
2025-09-24 16:07 ` [pve-devel] [PATCH qemu-server v2 1/1] fix #6613: pass purge param to delete_service_from_config Michael Köppl
2025-09-24 16:07 ` [pve-devel] [PATCH container " Michael Köppl
2025-09-24 16:07 ` [pve-devel] [PATCH widget-toolkit v2 1/1] window: add ConfirmRemoveDialog Michael Köppl
2025-09-26 14:15 ` Daniel Kral [this message]
2025-09-24 16:07 ` [pve-devel] [PATCH manager v2 1/2] ui: add ConfirmRemoveResource window Michael Köppl
2025-09-24 16:07 ` [pve-devel] [PATCH manager v2 2/2] ui: use ConfirmRemoveResource window for removing resources Michael Köppl
2025-09-24 16:07 ` [pve-devel] [PATCH docs v2 1/1] add notes about effects of purge flag for resource and guest removal Michael Köppl
2025-09-26 14:23 ` [pve-devel] [PATCH container/docs/ha-manager/manager/proxmox-widget-toolkit/qemu-server v2 0/8] fix #6613: update HA rules upon resource deletion Daniel Kral
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=DD2SMVLCEPE2.4MHT70UA7R9X@proxmox.com \
--to=d.kral@proxmox.com \
--cc=pve-devel-bounces@lists.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.