From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Aaron Lauterer <a.lauterer@proxmox.com>
Subject: Re: [pve-devel] [PATCH v3 manager 0/2] ui: ceph: improve discoverability of warning details
Date: Wed, 8 Mar 2023 17:43:28 +0100 [thread overview]
Message-ID: <a0bf371d-7e3e-7012-6daa-5ce2cb09ea3e@proxmox.com> (raw)
In-Reply-To: <380337b9-49aa-7fb6-3e29-8f751f6aa2be@proxmox.com>
Am 08/03/2023 um 17:38 schrieb Aaron Lauterer:
>> That said, why not avoid the tooltip but inline the info by moving the severity to
>> the right, dropping the info button completely and making the grid row expandable,
>> i.e., like the PMG tracking center grid does?
>
> We thought about it, but initially I wasn't too happy about it, because if the detailed error message has many lines and/or long lines, it would be nicer to just open the window and making it as large as possible.
You could still have a open-in window there if we really want, copy-button can
help too for some "copy to support/forum/text-editor-for-searching" - as at least
I use this mostly to get a quick overview or to extract info.
One advantage of expansion: you can have all errors in view, not just one at a
time (or well, per tab ^^)
prev parent reply other threads:[~2023-03-08 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 12:09 Aaron Lauterer
2023-03-08 12:09 ` [pve-devel] [PATCH v3 manager 1/2] ui: ceph: make the warning detail button stand out more Aaron Lauterer
2023-03-08 12:09 ` [pve-devel] [PATCH v3 manager 2/2] ui: ceph status: add tooltip with details to warnings Aaron Lauterer
2023-03-08 16:05 ` [pve-devel] [PATCH v3 manager 0/2] ui: ceph: improve discoverability of warning details Thomas Lamprecht
2023-03-08 16:38 ` Aaron Lauterer
2023-03-08 16: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=a0bf371d-7e3e-7012-6daa-5ce2cb09ea3e@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=a.lauterer@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