public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Matthias Heiserer <m.heiserer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [RFC manager 0/5] GUI: Hardware comments
Date: Mon, 14 Feb 2022 15:01:37 +0100	[thread overview]
Message-ID: <20220214140144.961041-1-m.heiserer@proxmox.com> (raw)

This series is a first attempt to fix 2672 by implementing editable comments
that are displayed in the GUI and stored in the qemu config file. 

It works, but there are several questions:

How should comments be displayed? (GUI)
    I added a third column. IMO, this looks cleaner than the alternative of
    appending the comment to the corresponding config values. However, it 
    requires more space and some special logic.
    
What to do when there is not enough space? (GUI)
    Currently, this case is not handled. A possible solution would be to
    wrap overflowing lines, but I'm not sure what opinions are on that.
    
Should comments of ineditable fields (EFI Disk) be editable? (GUI)
    I suppose yes, but currently they are not.

Currently missing are:
    GUI: Comments in the wizard, i.e. when creating a VM, no comment can be set.
    Detaching disks voids their comment. Probably shouldn't happen, but seems
        a tad complicated.
    The GUI assumes comments (except memory, socket, bios,  machine, scsihw)
        to be URIencoded. This could be verified server-side.

Generally, I tried to keep the code consistent, but didnt always succeed, partly
because of the variations in the original code.


Matthias Heiserer (5):
  GUI: Parser: add comment support
  GUI: Utils: add comment renderer and field provider
  GUI: QEMU Hardware: add comment column
  GUI: QEMU Hardware: multikey support for comments
  GUI: QEMU Hardware: add comment fields to rows

 www/manager6/Parser.js             | 22 +++++++++++++++
 www/manager6/Utils.js              | 39 +++++++++++++++++++++++++++
 www/manager6/qemu/AudioEdit.js     |  3 ++-
 www/manager6/qemu/CDEdit.js        |  7 ++---
 www/manager6/qemu/CIDriveEdit.js   |  2 ++
 www/manager6/qemu/DisplayEdit.js   |  2 +-
 www/manager6/qemu/HDEdit.js        |  4 +++
 www/manager6/qemu/HDEfi.js         |  3 +++
 www/manager6/qemu/HDTPM.js         |  2 ++
 www/manager6/qemu/HardwareView.js  | 43 +++++++++++++++++++++++++++++-
 www/manager6/qemu/MachineEdit.js   | 24 ++++++++++-------
 www/manager6/qemu/MemoryEdit.js    |  3 +++
 www/manager6/qemu/NetworkEdit.js   |  7 +++--
 www/manager6/qemu/PCIEdit.js       |  1 +
 www/manager6/qemu/ProcessorEdit.js |  1 +
 www/manager6/qemu/QemuBiosEdit.js  |  1 +
 www/manager6/qemu/RNGEdit.js       |  1 +
 www/manager6/qemu/ScsiHwEdit.js    | 15 ++++++-----
 www/manager6/qemu/SerialEdit.js    |  6 ++---
 www/manager6/qemu/USBEdit.js       | 13 ++++++++-
 20 files changed, 171 insertions(+), 28 deletions(-)

-- 
2.30.2





             reply	other threads:[~2022-02-14 14:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 14:01 Matthias Heiserer [this message]
2022-02-14 14:01 ` [pve-devel] [RFC manager 1/5] GUI: Parser: add comment support Matthias Heiserer
2022-02-14 14:01 ` [pve-devel] [RFC qemu-server 1/2] QEMU: add comment helper Matthias Heiserer
2022-02-14 14:01 ` [pve-devel] [RFC manager 2/5] GUI: Utils: add comment renderer and field provider Matthias Heiserer
2022-02-14 14:01 ` [pve-devel] [RFC qemu-server 2/2] QEMU: add comment fields Matthias Heiserer
2022-02-14 14:01 ` [pve-devel] [RFC manager 3/5] GUI: QEMU Hardware: add comment column Matthias Heiserer
2022-02-14 14:01 ` [pve-devel] [RFC manager 4/5] GUI: QEMU Hardware: multikey support for comments Matthias Heiserer
2022-02-14 14:01 ` [pve-devel] [RFC manager 5/5] GUI: QEMU Hardware: add comment fields to rows Matthias Heiserer
2022-02-14 14:27 ` [pve-devel] [RFC manager 0/5] GUI: Hardware comments 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=20220214140144.961041-1-m.heiserer@proxmox.com \
    --to=m.heiserer@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