public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, m.heiserer@proxmox.com
Cc: Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager] storage GUI: fix unintuitive sorting order
Date: Mon, 21 Feb 2022 09:32:53 +0100	[thread overview]
Message-ID: <7c867147-33b0-427c-4c6f-09fa84562d7f@proxmox.com> (raw)
In-Reply-To: <20220218104230.311652-1-m.heiserer@proxmox.com>

Am 18.02.22 um 11:42 schrieb Matthias Heiserer:
> The backups in the 'Backups' table in Storages are now initially
> sorted by column 'Name' ascending.
> 
> Previously, they were first sorted by 'vmid' descending, then by date
> descending. This was unintuitive as 'vmid' doesn't exist as column
> in the GUI, and only 'Date' displayed a sorting arrow.
> 
> Signed-off-by: Matthias Heiserer <m.heiserer@proxmox.com>
> ---
>  www/manager6/storage/BackupView.js | 6 +-----
>  1 file changed, 1 insertion(+), 5 deletions(-)
> 
Please note that the order was recently intentionally changed to be like
that, see commit 58f4e6ac387561a16ec370812083d60a12dc4cfe

That said, you do have a point. One way to improve the situation might
be to add a vmid column, but we could also think about using a tree view
for backups instead.

@Thomas: Would the latter be okay for you?

Not related to your change, but some more context:

PVE.storage.BackupView is currently derived from
PVE.storage.ContentView, but actually, it caused a lot of special
handling to be added to that base class. If PVE.storage.BackupView were
it's own thing (which is essentially implied if we go with the tree view
approach), PVE.storage.ContentView should also get simpler again.

There also is PVE.grid.BackupView which is used for backups of a single
guest and IMHO it should be merged with the other one, with a few config
options to account for the small differences in behavior.




  reply	other threads:[~2022-02-21  8:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18 10:42 Matthias Heiserer
2022-02-21  8:32 ` Fabian Ebner [this message]
2022-02-21  8:39   ` 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=7c867147-33b0-427c-4c6f-09fa84562d7f@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=m.heiserer@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.lamprecht@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal