From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Dominik Csapak" <d.csapak@proxmox.com>,
"Lukas Wagner" <l.wagner@proxmox.com>,
<pdm-devel@lists.proxmox.com>
Subject: Re: [PATCH datacenter-manager 3/3] ui: make the default dashboard page configurable
Date: Wed, 02 Sep 2026 13:54:59 +0200 [thread overview]
Message-ID: <DL4T7A1LNU2B.2REGVQ6U4UFK7@proxmox.com> (raw)
In-Reply-To: <78e8a07c-e905-4083-9fe6-d292fbf05865@proxmox.com>
On Wed Sep 2, 2026 at 1:10 PM CEST, Dominik Csapak wrote:
>>
>> - Have a 'My Settings' dialog in the user menu similar to PVE
>
> I would probably opt for this, since we already are missing
> some settings that would be nice here (e.g. xterm.js/novnc settings
> that we already have in PVE)
>
Seems good to me!
>>
>> - Abandon the local setting altogether and make it a per-user setting
>> that is stored in the backend. Might require bigger changes, since I
>> don't think we have any good way to store per-user properties right
>> now. Users that routinely use multiple browsers and/or devices might
>> prefer this over a local setting.
>>
>
> One of the biggest thing that makes me a bit hesitant to do this
> is that we don't usually have per user backend (gui) settings at all
>
> If we do want those here, I'd also like them on the PVE side
> (e.g. tree/view settings)
>
Yeah, it would definitely a much bigger undertaking. One where it
definitely makes sense to think about the cross-product implications.
I guess storing these settings in local storage *now* does not really stop
us from changing it later to a per-user, backend setting, if we think
that this would be a good idea, so no need to overthink this right now.
>>
>> What do you think?
>
> see above, currently I'd prefer to implementing a 'my settings' window.
>
> another option would be to have the global default set in the backend
> but this clashes a bit with the permissions per view etc...
>
>>
>> One further thing that I have noticed: If a view that is used as a
>> dashboard is deleted, we should probably fall back to the default
>> dashboard again. Otherwise user might complain about 'broken' dashboards
>> without a clear indication about what is wrong.
>
> yes that sounds sensible (at least as long as we only save it in
> the browser local storage. if we have a setting in the backend
> we could prevent deletion if anybody is using that or reset
> all users preferences)
>
Maybe the UI could then also show a small hint in the header, maybe
something like
"View xyz does not exist, showing default dashboard instead"
I guess if there is such a hint, we could also just shown an empty view
instead of the default dashboard, since then the user knows what's going
on.
prev parent reply other threads:[~2026-09-02 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 8:17 [PATCH datacenter-manager/yew-widget-toolkit 0/3] ui: make the default dashboard configurable Dominik Csapak
2026-08-20 8:17 ` [PATCH yew-widget-toolkit 1/3] state: event: add helpers for custom DOM events Dominik Csapak
2026-08-20 8:17 ` [PATCH yew-widget-toolkit 2/3] state: persistent state: allow listening for updates Dominik Csapak
2026-08-20 8:17 ` [PATCH datacenter-manager 3/3] ui: make the default dashboard page configurable Dominik Csapak
2026-09-02 8:26 ` Lukas Wagner
2026-09-02 11:10 ` Dominik Csapak
2026-09-02 11:54 ` Lukas Wagner [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=DL4T7A1LNU2B.2REGVQ6U4UFK7@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=d.csapak@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox