On 04.09.19 16:17, Stefan Reiter wrote: > Most of the code is adapted from KVComboBox, from which it inherited > before, with some generic code removed. > > The templating code adds a header for every group transition it > encounters, thus providing support for arbitrary groups (e.g. custom > models in the future).
Hmm, while this seems like a small improvement to the status quo. I'd rather like to see a variant which shows less to the user at first sight, to not overload them with to many choices. Something with more levels or collapsible types could help here. Dominik had an idea that we could try to use a ComboGrid here, Grids have a grouping feature, you can see it in action for available Node Updates, there we group by "Vendor" (Proxmox or Debian). You could try if that feature works in the ComboGrid use case too, or if it's easy to make it work there, and see if that looks like a good alternative - providing better UX. > > Signed-off-by: Stefan Reiter <s.rei...@proxmox.com> > --- > > v2: Give licensing rights of the Athlon series back to it's rightful owner AMD > (v1 had 'athlon' as Intel by mistake) > > > www/css/ext6-pve.css | 11 ++ > www/manager6/form/CPUModelSelector.js | 151 ++++++++++++++++++++------ > 2 files changed, 128 insertions(+), 34 deletions(-) > _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
