From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Proxmox Datacenter Manager development discussion"
<pdm-devel@lists.proxmox.com>,
"Michael Köppl" <m.koeppl@proxmox.com>
Subject: Re: [pdm-devel] [PATCH datacenter-manager 3/4] ui: pbs: move node overview to tab and add update tab
Date: Fri, 21 Nov 2025 09:25:21 +0100 [thread overview]
Message-ID: <DEE89I5BQDVI.12ARSUU4AVQB@proxmox.com> (raw)
In-Reply-To: <DEDN4XZPY9SN.2MUV8EBSX50VM@proxmox.com>
On Thu Nov 20, 2025 at 4:52 PM CET, Michael Köppl wrote:
>> +struct PbsNodePanelComp;
>> +
>> +impl yew::Component for PbsNodePanelComp {
>> + type Message = ();
>> + type Properties = PbsNodePanel;
>> +
>> + fn create(_ctx: &yew::Context<Self>) -> Self {
>> + Self
>> + }
>> +
>> + fn changed(&mut self, ctx: &Context<Self>, old_props: &Self::Properties) -> bool {
>> + let props = ctx.props();
>> +
>> + props.remote != old_props.remote
>> + }
>> +
>> + fn view(&self, ctx: &yew::Context<Self>) -> yew::Html {
>> + let props = ctx.props();
>> +
>> + let title: Html = Row::new()
>> + .gap(2)
>> + .class(AlignItems::Baseline)
>> + .with_child(Fa::new("building"))
>> + .with_child(tr!("Node"))
>
> nit: I might not be entirely up-to-date on the nomenclature, but is
> "Node" correct here? IMO it also looked a bit off, having
> "Remote '<name>'" on the left panel and then just "Node" on the right
> panel. Perhaps "Backup Server", "Proxmox Backup Server", or the name of
> the PBS might fit better in this case? Was there a reason to use "Node"?
>
Thank you for the review, first and foremost!
Good catch - I also wasn't super sure about what to put here.
Main reason why I went with 'Node' is consistency with the PVE variant
of the view. There, the label is 'Node {nodename}', just so to clarify
that the data in the graphs is from the specific node selected in the
resource tree on the left-hand side.
For PBS, we only have one node per remote (for which we also don't
really know the hostname); and 'Node localhost' is not really that
useful - hence I just went with 'Node'.
Would you still rather use some other string here?
>> + .into();
>> +
>> + TabPanel::new()
>> + .class(pwt::css::FlexFit)
>
>
>
> _______________________________________________
> pdm-devel mailing list
> pdm-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
next prev parent reply other threads:[~2025-11-21 8:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 10:36 [pdm-devel] [PATCH datacenter-manager 0/4] add 'Updates' tab for PBS remotes Lukas Wagner
2025-11-20 10:36 ` [pdm-devel] [PATCH datacenter-manager 1/4] ui: move pbs node overview panel from pbs::remote to pbs::node::overview Lukas Wagner
2025-11-20 10:36 ` [pdm-devel] [PATCH datacenter-manager 2/4] ui: pbs: rename RemoteOverviewPanel to PbsNodeOverviewPanel Lukas Wagner
2025-11-20 10:36 ` [pdm-devel] [PATCH datacenter-manager 3/4] ui: pbs: move node overview to tab and add update tab Lukas Wagner
2025-11-20 15:52 ` Michael Köppl
2025-11-21 8:25 ` Lukas Wagner [this message]
2025-11-20 10:36 ` [pdm-devel] [PATCH datacenter-manager 4/4] ui: pve: rename NodePanel to PveNodePanel Lukas Wagner
2025-11-20 15:56 ` [pdm-devel] [PATCH datacenter-manager 0/4] add 'Updates' tab for PBS remotes Michael Köppl
2025-11-21 9:32 ` [pdm-devel] applied: " 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=DEE89I5BQDVI.12ARSUU4AVQB@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=m.koeppl@proxmox.com \
--cc=pdm-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.