public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Lukas Wagner <l.wagner@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Maximiliano Sandoval <m.sandoval@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager 1/2] ui: dc: backup: improve UX for the different 'notification-mode's
Date: Mon, 15 Apr 2024 11:27:03 +0200	[thread overview]
Message-ID: <c4ebec01-8e22-4fde-b820-ec99f04de845@proxmox.com> (raw)
In-Reply-To: <34eb2ab5-4022-4630-9baf-d5466ba32c0c@proxmox.com>

On  2024-04-11 09:44, Thomas Lamprecht wrote:
>> Tested both commits, they do what they promise.
>>
>>> +	let notificationSystemHint = Ext.create({
>>> +	    xtype: 'displayfield',
>>> +	    padding: '0 0 0 5',
>>> +	    userCls: 'pmx-hint',
>>> +	    hidden: true,
>>> +	    value: gettext('No email configured, the notification system will be used'),
>>> +	    viewModel,
>>> +	    bind: {
>>> +		hidden: '{!hintTextVisible}',
>>
>> I think the `pmx-hint` being displayed as yellow suggests it is a
>> warning/error rather than a hint. I wonder if there is a better
>> approach, as this is certainly not a warning.
> 
> Yeah, the hint is even often used as warning, having something more like a
> "notice" or well, actual "hint" level, that isn't as flashy, might be a
> good idea in the long run..
> 
> For now, we could also set a 'Hint' label and then add the pmx-hint class only
> to the labelClsExtra config?
> 
> But I'm fine with this as is if you, Lukas, think that it's warranted (and
> maybe even not showed that often in practice anyway).

Actually this is visible when creating new backup jobs, because 'Notification mode' is 
set to 'Default (auto)' and there is no email entered. So yeah, a more gentle 
hint would be better. That being said, I'd like to get this merged ASAP to
resolve pontential for confusion for our users[1].

I would suggest to merge the variant with 'pmx-hint' (I'll send a v2 though, because
I fixed a minor issue just now when reevaluating this) and then revisit
this soonish to introduce a more hinty, less warning CSS class. There are other places where
that one could be useful (e.g. second page of the same dialog - Retention, or Rentention
settings for storage plugins), so we could fix them all in one go in a followup.


[1] https://forum.proxmox.com/threads/pve-sending-email-notifications-on-successful-backup-jobs.136768/post-635769
-- 
- Lukas




  reply	other threads:[~2024-04-15  9:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23 16:09 Lukas Wagner
2023-11-23 16:09 ` [pve-devel] [PATCH manager 2/2] ui: one-off backup: show hint if notification-system is used Lukas Wagner
2023-12-14 10:26 ` [pve-devel] [PATCH manager 1/2] ui: dc: backup: improve UX for the different 'notification-mode's Maximiliano Sandoval
2024-04-11  7:44   ` Thomas Lamprecht
2024-04-15  9:27     ` Lukas Wagner [this message]
2024-01-08 10:43 ` Lukas Wagner
2024-02-16 10:35   ` Lukas Wagner
2024-04-09  9:22 ` Maximiliano Sandoval

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=c4ebec01-8e22-4fde-b820-ec99f04de845@proxmox.com \
    --to=l.wagner@proxmox.com \
    --cc=m.sandoval@proxmox.com \
    --cc=pve-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