From: Matthias Heiserer <m.heiserer@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager v5 05/11] ui: add form/TagColorGrid
Date: Fri, 8 Apr 2022 13:39:56 +0200 [thread overview]
Message-ID: <7d20889e-8309-0ae2-55c3-36b27f9a3a34@proxmox.com> (raw)
In-Reply-To: <20220408074530.1212056-10-d.csapak@proxmox.com>
On 08.04.2022 09:45, Dominik Csapak wrote:
8<
> +
> + setValue: function(value) {
> + let me = this;
> + me.setColor(value);
> + if (value && value.length === 6) {
> + me.picker.value = value[0] !== '#' ? `#${value}` : value;
> + }
> + },
> +
> + setColor: function(value) {
> + let me = this;
> + let oldValue = me.realvalue;
> + me.realvalue = value;
> + let color = value.length === 6 ? `#${value}` : undefined;
> + me.down('#picker').setStyle('background-color', color);Not a big fan of this initially being white. Makes it somewhat hard to
discover.
8<
> +
> +Ext.define('PVE.form.TagColorGrid', {
> + extend: 'Ext.grid.Panel',
> + alias: 'widget.pveTagColorGrid',
> +
> + mixins: [
> + 'Ext.form.field.Field',
> + ],
> +
I don't like how the selection in the grid works. I.e. one has to click
the sliver of whitespace between the columns to select a row, while
writing doesn't change the selected column.
8<---
> + },
> + ],
> +
> + columns: [
> + {
> + header: 'Tag',
> + dataIndex: 'tag',
> + xtype: 'widgetcolumn',
> + onWidgetAttach: function(col, widget, rec) {
> + widget.getStore().setData(PVE.Utils.tagList.map(v => ({ tag: v })));
> + },
> + widget: {
> + xtype: 'combobox',
> + isFormField: false,
> + maskRe: /[a-zA-Z0-9_.-]/,
As it gets used several times in different locations (form/Tag), you
could consider storing it in a fixed place.
8<---
next prev parent reply other threads:[~2022-04-08 11:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 7:45 [pve-devel] [PATCH cluster/widget-toolkit/manager v5] add tags to ui Dominik Csapak
2022-04-08 7:45 ` [pve-devel] [PATCH cluster v5 1/3] add CFS_IPC_GET_GUEST_CONFIG_PROPERTIES method Dominik Csapak
2022-04-08 10:05 ` Matthias Heiserer
2022-04-08 7:45 ` [pve-devel] [PATCH cluster v5 2/3] Cluster: add get_guest_config_properties Dominik Csapak
2022-04-08 7:45 ` [pve-devel] [PATCH cluster v5 3/3] datacenter.cfg: add option for tag-tree-style and tag-colors Dominik Csapak
2022-04-08 7:45 ` [pve-devel] [PATCH widget-toolkit v5 1/1] add tag related helpers Dominik Csapak
2022-04-08 7:45 ` [pve-devel] [PATCH manager v5 01/11] api: /cluster/resources: add tags to returned properties Dominik Csapak
2022-04-08 7:45 ` [pve-devel] [PATCH manager v5 02/11] api: /version: add 'tag-colors' and 'tag-tree-style' Dominik Csapak
2022-04-08 7:45 ` [pve-devel] [PATCH manager v5 03/11] ui: parse and save tag color overrides from /version Dominik Csapak
2022-04-08 7:45 ` [pve-devel] [PATCH manager v5 04/11] ui: tree/ResourceTree: collect tags on update Dominik Csapak
2022-04-08 7:45 ` [pve-devel] [PATCH manager v5 05/11] ui: add form/TagColorGrid Dominik Csapak
2022-04-08 11:39 ` Matthias Heiserer [this message]
2022-04-08 7:45 ` [pve-devel] [PATCH manager v5 06/11] ui: dc/OptionView: add editors for tag settings Dominik Csapak
2022-04-08 7:45 ` [pve-devel] [PATCH manager v5 07/11] ui: add form/Tag Dominik Csapak
2022-04-08 7:45 ` [pve-devel] [PATCH manager v5 08/11] ui: add form/TagEdit.js Dominik Csapak
2022-04-08 7:45 ` [pve-devel] [PATCH manager v5 09/11] ui: {lxc, qemu}/Config: show Tags and make them editable Dominik Csapak
2022-04-08 7:45 ` [pve-devel] [PATCH manager v5 10/11] ui: tree/ResourceTree: show Tags in tree Dominik Csapak
2022-04-08 7:45 ` [pve-devel] [PATCH manager v5 11/11] ui: form/GlobalSearchField: display tags and allow to search for them Dominik Csapak
2022-04-08 12:15 ` [pve-devel] [PATCH cluster/widget-toolkit/manager v5] add tags to ui Matthias Heiserer
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=7d20889e-8309-0ae2-55c3-36b27f9a3a34@proxmox.com \
--to=m.heiserer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox