all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pve-devel] [RFC PATCH manager 3/3] ui: enable multiColumnSort for storage backup content
Date: Thu, 20 Apr 2023 15:39:37 +0200	[thread overview]
Message-ID: <019c09b0-3203-99f1-4e2d-aa9bfe0f78e5@proxmox.com> (raw)
In-Reply-To: <20230420080616.836255-3-d.csapak@proxmox.com>

I tried the series including this patch and yeah... sorting becomes very 
unpredicatable and weird. AFAICT it also depends on which order the last 3 
columns are selected.

The old behavior was that it was first sorted by VMID and then within the VMID 
by date right?
Is there a way to group by row property in ExtJS grids?

I personally would probably not use this patch.

On 4/20/23 10:06, Dominik Csapak wrote:
> this enables the user to sort the grid by multiple columns
> simultaneously, e.g. by vmid and then by date
> 
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> sending as rfc because i'm not so sure about this.
> 
> on one hand, this allows to recreate the original sorting if users want
> that, but the selection is a bit weird. there is no way to 'unsort'
> columns again, it simply uses the last 3 columns that were clicked
> 
> especially with the last patch (statefulness) it becomes weird, but
> maybe we want this more than we want it to be stateful?
> 
>   www/manager6/storage/BackupView.js | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/www/manager6/storage/BackupView.js b/www/manager6/storage/BackupView.js
> index bb045f5b6..ebc476747 100644
> --- a/www/manager6/storage/BackupView.js
> +++ b/www/manager6/storage/BackupView.js
> @@ -5,6 +5,7 @@ Ext.define('PVE.storage.BackupView', {
>   
>       showColumns: ['name', 'notes', 'protected', 'date', 'format', 'size'],
>   
> +    multiColumnSort: true,
>       stateful: true,
>       stateId: 'storage-backup-content',
>   




  reply	other threads:[~2023-04-20 13:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20  8:06 [pve-devel] [PATCH manager 1/3] fix #4678: ui: don't sort storage backup content by vmid by default Dominik Csapak
2023-04-20  8:06 ` [pve-devel] [PATCH manager 2/3] ui: make storage backup content stateful Dominik Csapak
2023-04-22  7:21   ` Thomas Lamprecht
2023-04-20  8:06 ` [pve-devel] [RFC PATCH manager 3/3] ui: enable multiColumnSort for storage backup content Dominik Csapak
2023-04-20 13:39   ` Aaron Lauterer [this message]
2023-04-22  7:21   ` Thomas Lamprecht
2023-04-22  7:38 ` [pve-devel] [PATCH manager 1/3] fix #4678: ui: don't sort storage backup content by vmid by default Thomas Lamprecht
2023-04-22  7:52   ` Thomas Lamprecht

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=019c09b0-3203-99f1-4e2d-aa9bfe0f78e5@proxmox.com \
    --to=a.lauterer@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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal