Re: [pbs-devel] [PATCH proxmox-backup 1/4] www: don't default to hourly sync job schedule

[Thomas Lamprecht <t.lamprecht@proxmox.com>]

On 04.11.20 14:46, Fabian Grünbichler wrote:
> On November 4, 2020 2:38 pm, Thomas Lamprecht wrote:
>> On 04.11.20 14:10, Fabian Grünbichler wrote:
>>> this breaks editing disabled sync jobs, and is also not consistent with
>>
>> just means that we should only set it onCreate..
> 
> also fine for me.
> 
>>> the backend defaults.
>>
>> which is? FWICT, there's no default in the backend - I want one here,
>> this can be easily edited and it's just better UX to avoid more decisions
>> which at this point may not be clear.
> 
> the backend's default is None/no schedule. for such simply values I 
> don't see much value in having a different default in the GUI, but I 
> don't care much either way.

A default for the backend would be a bit subtle and hard to change, if we'd like
to do so in the future. In the UI it's clearly presented to the user, they can
easily change it and we're pretty free to adapt it there if feedback shows that
would be better.

One should IMO not see the UI as plain "HTML form" like extension of an API, if it
would be that easy we could just auto generate it :)

> 
> for users that don't know much about sync jobs it might not be that 
> obvious how to have no schedule or even that that is an option when 
> creating a new one (you manually have to delete the value in the 
> picker/combobox).
> 

creating a new job without schedule seldom makes sense, I'd argue. Also, that it can
be temporarily be paused by deleting the schedule is subtle anyway, and IMO bad UX.
Not setting a default does not helps to suggest that is the case either, if we
want to make this clear, an explicit enable/disable checkbox which enables/disables
also the schedule field could be added.

But, an user also can just delete the job entry, if they just need to disable it and
cannot relate to the "clear schedule == disable", there's no relevant state full
information bound to a job. So, I do not see the need for it.


Again, to much words and pedantry for such a simple thing, sorry about that :-)