public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Dominik Csapak <d.csapak@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH manager v3 0/6] fix #1408: ui: make tree sorting configurable
Date: Wed, 22 Feb 2023 11:43:28 +0100	[thread overview]
Message-ID: <b88350f0-d018-edc3-ad2c-a80ddd56c6d1@proxmox.com> (raw)
In-Reply-To: <20230222075152.982943-1-d.csapak@proxmox.com>

Am 22/02/2023 um 08:51 schrieb Dominik Csapak:
> this series allows configuring the sorting of the resource tree
> 
> options are the sort-field, if guest types are grouped and if templates
> are grouped seperately. it's configurable via browser local storage
> 
> the first 2 patches are not really related but popped up during
> development
> 
> changes from v2:
> * improved browser local storage notice
> * added padding between the view selector and the button
> 
> changes from v1:
> * drop the datacenter config options for now
> * rename TreeSortingEdit into TreeSortingEdit
> * since we don't have a fallback besides the default, display the
>   defauls in the dropdowns
> * don't use booleanfield anymore (because of above change)
> * rename sp into localStorage
> * use fieldDefaults
> * refactor stuff into PVE.UIOptions (a new singleton)
> * remove storage view
> * remove booleanfield()
> 
> Dominik Csapak (6):
>   ui: remove 'Storage View'
>   ui: remove unused booleanfield
>   ui: refactor ui option related methods into UIOptions
>   ui: refactor refreshing the the resource store/tree
>   ui: add window for changing tree related options
>   fix #1408: ui: ResourceTree: sort the tree according to tree-sorting
>     options
> 

applied, thanks!

As talked off-list, I made three small followups
1) make settings button stand less out
2) making window a bit wider and claryfing the field labels (mostly that the
   type grouping only affects guests)
3) change the bogus url to '#'

for the record only, as we also talked off list: it might be nice to apply
changes live, so that one can see the effect in the background already.

But the current settings are relatively straight forward and after initial
setup its unlikely to change, so there's not _that_ much friction as is.




      parent reply	other threads:[~2023-02-22 10:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22  7:51 [pve-devel] " Dominik Csapak
2023-02-22  7:51 ` [pve-devel] [PATCH manager v3 1/6] ui: remove 'Storage View' Dominik Csapak
2023-02-22  7:51 ` [pve-devel] [PATCH manager v3 2/6] ui: remove unused booleanfield Dominik Csapak
2023-02-22  7:51 ` [pve-devel] [PATCH manager v3 3/6] ui: refactor ui option related methods into UIOptions Dominik Csapak
2023-02-22  7:51 ` [pve-devel] [PATCH manager v3 4/6] ui: refactor refreshing the the resource store/tree Dominik Csapak
2023-02-22  7:51 ` [pve-devel] [PATCH manager v3 5/6] ui: add window for changing tree related options Dominik Csapak
2023-02-22  7:51 ` [pve-devel] [PATCH manager v3 6/6] fix #1408: ui: ResourceTree: sort the tree according to tree-sorting options Dominik Csapak
2023-02-22 10:43 ` Thomas Lamprecht [this message]

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=b88350f0-d018-edc3-ad2c-a80ddd56c6d1@proxmox.com \
    --to=t.lamprecht@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal