public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] applied: [PATCH proxmox-backup 3/5] ui: datastore content: add context menu to groups and snapshots
Date: Wed, 29 Nov 2023 08:35:56 +0100	[thread overview]
Message-ID: <3617045f-a415-4ce0-9548-9f7c83b14943@proxmox.com> (raw)
In-Reply-To: <2dfe28d8-8f26-496d-9da8-9f3bcb99b15c@proxmox.com>

On 11/28/23 16:27, Thomas Lamprecht wrote:
> Am 28/11/2023 um 10:44 schrieb Dominik Csapak:
>> and show the relevant actions. They will be forwarded to the controller,
>> so we can reuse that code without big refactoring them into another
>> class/place.
>>
>> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
>> ---
>> sadly no keyboard navigation in there.. but i'm looking into it
>>
>>   www/datastore/Content.js | 114 +++++++++++++++++++++++++++++++++++++++
>>   1 file changed, 114 insertions(+)
>>
>>
> 
> applied this one for now, thanks!
> 
> Albeit, I'm wondering if we should add the ID into the menu header, for
> snapshots that tends to be a bit large though...

yeah i tried that, but couldn't make it look ok and consistent, so i left it out.
If you have an idea how to format it (maybe "type \n id \n time" ?)
it should be relatively trivial to implement.

> 
> Oh, and fwiw, we could add a "Copy Text" for the cells where it makes
> sense (ID of group or snapshot, comment firt line, maybe date) so that
> one has it slightly easier if they found the wanted snapshot/group here
> and what to use that ID for, e.g., finding that in the PVE storage
> content UI, but no hard feelings, just as an idea.

yeah that could make sense, or maybe easier if we allow selecting the
text of the cells directly? that way the users can select copy themselves.
(we'd have to show the context menu depending on if text is selected or
not of course, but that should be doable without much issues)




  reply	other threads:[~2023-11-29  7:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28  9:43 [pbs-devel] [PATCH proxmox-backup 0/5] add context menu to datastore content Dominik Csapak
2023-11-28  9:43 ` [pbs-devel] [PATCH proxmox-backup 1/5] api-types: add an UploadStatistic api type Dominik Csapak
2023-11-28  9:43 ` [pbs-devel] [PATCH proxmox-backup 2/5] api: datastore admin: add 'snapshot-information' api call Dominik Csapak
2023-11-28  9:44 ` [pbs-devel] [PATCH proxmox-backup 3/5] ui: datastore content: add context menu to groups and snapshots Dominik Csapak
2023-11-28 15:27   ` [pbs-devel] applied: " Thomas Lamprecht
2023-11-29  7:35     ` Dominik Csapak [this message]
2023-11-29  7:47       ` Thomas Lamprecht
2023-11-28  9:44 ` [pbs-devel] [PATCH proxmox-backup 4/5] ui: datastore content: add snapshot information to context menu Dominik Csapak
2023-11-28  9:44 ` [pbs-devel] [PATCH proxmox-backup 5/5] ui: datastore content: add 'more actions' menu to actions Dominik Csapak
2023-11-28 11:32 ` [pbs-devel] [PATCH proxmox-backup 0/5] add context menu to datastore content Fabian Grünbichler
2023-11-28 12:48 ` Philipp Hufnagl
2023-11-28 13:41 ` Max Carrara

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=3617045f-a415-4ce0-9548-9f7c83b14943@proxmox.com \
    --to=d.csapak@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    --cc=t.lamprecht@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