public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: Aaron Lauterer <a.lauterer@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [RFC PATCH manager 4/4] ui: pci mapping: rework mapping panel for better user experience
Date: Tue, 20 Jun 2023 12:48:53 +0200	[thread overview]
Message-ID: <76e33b7d-c564-29b0-d076-01fc01968322@proxmox.com> (raw)
In-Reply-To: <23bab32a-abc9-52a4-e4b9-3f35c9c5547f@proxmox.com>

On 6/20/23 12:18, Aaron Lauterer wrote:
> 
> 
> On 6/20/23 11:57, Dominik Csapak wrote:
>> On 6/20/23 11:35, Aaron Lauterer wrote:
>>> I like the approach as it cleans up the overloaded tbar that has items that are only valid in 
>>> certain contexts.
>>>
>>> Two small nits from a UX POV:
>>>
>>> - double clicking any PCI device should open the edit dialog for the node, similar to double 
>>> clicking the node itself
>>
>> makes sense imo
>>
>>> - the Action Column should probably be further left and not on the far right side by default. I 
>>> personally like it to be the second column from the left as all other columns are rather informal.
>>
>> mhmm can do that, but how i refactored that seems to be a bit hacky to inject an actioncolumn at a
>> certain position, but technically not a problem
> 
> But aren't we doing that already in the content view of PBS? AFAIK it is the 3rd column there.
> 
>

sorry i didn't describe it properly. ofc it's possible to have the actioncolumn at any position
it's just that the way i have structured the code makes it slightly weird to do
(the columns are defined in the subclasses, but the actioncolumn would be injected in
the base class, so i'd have to split the columns array before inserting it)





  reply	other threads:[~2023-06-20 10:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19 14:13 [pve-devel] [PATCH manager 1/4] ui: resource map tree: make 'ok' status clearer Dominik Csapak
2023-06-19 14:13 ` [pve-devel] [PATCH manager 2/4] ui: pci map edit: reintroduce warnings checks Dominik Csapak
2023-06-20 12:16   ` Fiona Ebner
2023-06-19 14:13 ` [pve-devel] [PATCH manager 3/4] ui: pci map edit: improve new host mappings dialog Dominik Csapak
2023-06-20 12:34   ` Fiona Ebner
2023-06-19 14:13 ` [pve-devel] [RFC PATCH manager 4/4] ui: pci mapping: rework mapping panel for better user experience Dominik Csapak
2023-06-20  9:35   ` Aaron Lauterer
2023-06-20  9:57     ` Dominik Csapak
2023-06-20 10:18       ` Aaron Lauterer
2023-06-20 10:48         ` Dominik Csapak [this message]
2023-06-20 13:25   ` Fiona Ebner
2023-06-20 14:13     ` Dominik Csapak

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=76e33b7d-c564-29b0-d076-01fc01968322@proxmox.com \
    --to=d.csapak@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal