From: Lukas Wagner <l.wagner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH widget-toolkit 2/2] repo view: replace non-clickable checkbox with Yes/No text
Date: Fri, 20 Jan 2023 12:17:12 +0100 [thread overview]
Message-ID: <20230120111712.243308-3-l.wagner@proxmox.com> (raw)
In-Reply-To: <20230120111712.243308-1-l.wagner@proxmox.com>
From a usability view, having a checkbox that is not clickable is pretty
misleading, especially if the visual style is exactly the same as in
other places in the UI where the checkbox is functional.
Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
---
src/node/APTRepositories.js | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/src/node/APTRepositories.js b/src/node/APTRepositories.js
index ce8f718..1c4a08c 100644
--- a/src/node/APTRepositories.js
+++ b/src/node/APTRepositories.js
@@ -239,11 +239,10 @@ Ext.define('Proxmox.node.APTRepositoriesGrid', {
columns: [
{
- xtype: 'checkcolumn',
header: gettext('Enabled'),
- dataIndex: 'Enabled',
- listeners: {
- beforecheckchange: () => false, // veto, we don't want to allow inline change - to subtle
+ dataindex: 'Enabled',
+ renderer: function(_a, _b, data) {
+ return data?.data?.Enabled ? Proxmox.Utils.yesText : Proxmox.Utils.noText;
},
width: 90,
},
--
2.30.2
next prev parent reply other threads:[~2023-01-20 11:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 11:17 [pve-devel] [PATCH manager/widget-toolkit 0/2] ui: replace non-clickable checkboxes " Lukas Wagner
2023-01-20 11:17 ` [pve-devel] [PATCH manager 1/2] ui: backup: replication: replace non-clickable checkbox " Lukas Wagner
2023-01-20 11:17 ` Lukas Wagner [this message]
2023-01-20 14:09 ` [pve-devel] [PATCH manager/widget-toolkit 0/2] ui: replace non-clickable checkboxes " Thomas Lamprecht
2023-01-23 10:46 ` Lukas Wagner
2023-01-23 10:57 ` Thomas Lamprecht
2023-01-23 11:01 ` Lukas Wagner
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=20230120111712.243308-3-l.wagner@proxmox.com \
--to=l.wagner@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox