IMO the behavior was really dangerous prev., possibly causing
downtime of API accessing stuff with a single mistaken click.
Follow our general pattern and ask for confirmation
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
to prevent that they further diverge than they alread have
(pmxInfoWidget got an additional function that is compatible)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
they live there now, so we can delete them here and use the ones from
widget-toolkit instead
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
To better match the gauge in the current status infobox in the same
summary panel, which is already using a format where KiB is 1024
the latter needs a (not yet bumped) widget toolkit update to 2.5-2 or
newer, just setting now to avoid forgetting it.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
this is not something one really questions when not there, so avoid
adding a extra overly specific translation as "No Data" fits quite
well..
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
in case a zpool has not been yet scrubbed, there is no 'scan'
information in `zpool status` output.
Adding a informational text in that case might help users to notice
that something is not configured optimally (e.g. disabled cronjob)
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
As else some people could be confused and put in their name, as below
is the email field, and name+email are quite often pairs.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
by increasing the space for the link, and using a boxLabel instead
of fieldLabel, which has better spacing for longer text
also move the e-mail before the directory to have all textboxes together
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
if the 'default' account exists, make the name field required and
remove the emptytext
get the information by querying the grid store. this may be not
up-to-date, but it is less intrusive that an extra api call that
blocks the window
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
to order a ceritificate, we need at least one configured domain, and
the configured account (or default) must exist
so track the domaincount in the viewmodel and introduce a
'canOrder' formula which is only true when domaincount > 0 and
account is set (if the configured account does not exist, or no account
exists at all we set 'account' to 'null')
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
instead of using API2Request manually, just reload the store of
the accountselector and check if the configured account is in it
this should fix the spurious loading mask of the panel when
loading the accounts
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
It's not 100% true, but for the user more understandable. IF we
actually change such that this detail matters we can still go for a
"Better" solution then, as it will need UI updates anyway..
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
