public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>,
	Hannes Laimer <h.laimer@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup v4 2/6] ui: add support for optional Remote in SyncJob
Date: Tue, 3 Oct 2023 19:13:41 +0200	[thread overview]
Message-ID: <ee663e70-ba3c-4a03-bd30-f1540b4f6eb7@proxmox.com> (raw)
In-Reply-To: <20230929124901.179405-3-h.laimer@proxmox.com>

Am 29/09/2023 um 14:48 schrieb Hannes Laimer:
> diff --git a/www/window/SyncJobEdit.js b/www/window/SyncJobEdit.js
> index 48a0c7a9..1d3b021f 100644
> --- a/www/window/SyncJobEdit.js
> +++ b/www/window/SyncJobEdit.js
> @@ -135,15 +135,25 @@ Ext.define('PBS.window.SyncJobEdit', {
>  
>  		column2: [
>  		    {
> -			fieldLabel: gettext('Source Remote'),
> +			fieldLabel: gettext('Source PBS'),

We avoid using the product abbreviations in UI, docs and marketing
whenever possible.

And I do not like it too much that this is optional, that allows
for easier errors and feels a bit odd w.r.t. how we do things in
the rest of the UI.

From the top of my head I can see two options (without a bigger
refactoring/split):

1. use "Source Server" as field label and keep it required, make
   the local server a special entry in the selection, i.e., one
   with nothing in the remote id (or "-") and localhost in the
   Host column.

2. Add a radio-group with two options like:

   Source: ( ) Remote Datastore ( ) Local Datastore

   If Local datastore is selected the remote field gets disabled
   completely. This is a bit more explicit w.r.t. UX, but takes
   up more form space.

Maybe there are better ideas, I mean we could also transform this
whole add-sync-job to a wizard style dialog, but I do not want
to move the goalposts of this series such far (as such a change
surely would have a lot of bike shedding potential on its own).




  reply	other threads:[~2023-10-03 17:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 12:48 [pbs-devel] [PATCH proxmox-backup v4 0/6] local sync-jobs Hannes Laimer
2023-09-29 12:48 ` [pbs-devel] [PATCH proxmox-backup v4 1/6] api2: make Remote for SyncJob optional Hannes Laimer
2023-09-29 12:48 ` [pbs-devel] [PATCH proxmox-backup v4 2/6] ui: add support for optional Remote in SyncJob Hannes Laimer
2023-10-03 17:13   ` Thomas Lamprecht [this message]
2023-09-29 12:48 ` [pbs-devel] [PATCH proxmox-backup v4 3/6] manager: add completion for opt. " Hannes Laimer
2023-09-29 12:48 ` [pbs-devel] [PATCH proxmox-backup v4 4/6] accept a ref to a HttpClient Hannes Laimer
2023-09-29 12:49 ` [pbs-devel] [PATCH proxmox-backup v4 5/6] pull: refactor pulling from a datastore Hannes Laimer
2023-09-29 12:49 ` [pbs-devel] [PATCH proxmox-backup v4 6/6] pull: add support for pulling from local datastore Hannes Laimer
2023-10-03 17:17 ` [pbs-devel] [PATCH proxmox-backup v4 0/6] local sync-jobs 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=ee663e70-ba3c-4a03-bd30-f1540b4f6eb7@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=h.laimer@proxmox.com \
    --cc=pbs-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