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 manager v2 1/2] ui: tasks: add actioncolumn to open task
Date: Sat, 16 Nov 2024 17:04:01 +0100 [thread overview]
Message-ID: <fc024b75-065a-4f79-a5af-3f631ba7684d@proxmox.com> (raw)
In-Reply-To: <20241111155043.369360-2-a.lauterer@proxmox.com>
Am 11.11.24 um 16:50 schrieb Aaron Lauterer:
> Many (new) users don't realize that the task view can be used to open
> the task details.
> By adding a small action column we can have a button to open the task as
> well, next to double clicking it.
>
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
> ---
> Since the record is fetched quite differently than in the regular
> handler, and we don't necessarily have a selection on the right row at
> this point, I opted to create the window right in the dedicated handler.
>
> The other sensible approach would be to factor out the window opening
> from `run_task_viewer` into a new function. But since that function
> would just open the window I decided against it.
>
> Not sure if we want the above explanation in the commit msg. If so, feel
> free to put it there when applying the patch.
>
> Regarding the icon: I went with the chevron-right as this is what we use
> in the UI of the backup server. Alternatively the `fa-eye` might also be
> fitting.
Looks fine code-wise, but we got some inconsistency with these things:
- PBS uses the same icon but uses "Open Task" as tooltip
- our dedicated Task panel, used for the per-node or per-guest task logs
is using "View" as button text with fa-window-restore as icon.
Also, it would be good to think over if it makes sense adding the action
column there too, albeit I'm not having problems with skipping that for
now
fa-eye is IMO worse on its own and, more objectively, as that it further
increases the grade of inconsistency.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-11-16 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 15:50 [pve-devel] [PATCH manager v2 0/2] ui: tasks: add button " Aaron Lauterer
2024-11-11 15:50 ` [pve-devel] [PATCH manager v2 1/2] ui: tasks: add actioncolumn " Aaron Lauterer
2024-11-16 16:04 ` Thomas Lamprecht [this message]
2024-11-11 15:50 ` [pve-devel] [PATCH manager v2 2/2] ui: tasks: use autoshow instead of win.show Aaron Lauterer
2024-11-16 15:58 ` [pve-devel] applied: " Thomas Lamprecht
2024-11-18 10:49 ` [pve-devel] [PATCH manager v2 0/2] ui: tasks: add button to open task Aaron Lauterer
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=fc024b75-065a-4f79-a5af-3f631ba7684d@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