From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: [pbs-devel] applied-series: [PATCH widget-toolkit/proxmox-backup] improve Administration/Task panel
Date: Tue, 3 Nov 2020 14:52:57 +0100 [thread overview]
Message-ID: <353dbddf-c9b4-9b41-b585-85f006e9cfb7@proxmox.com> (raw)
In-Reply-To: <20201030140215.13329-1-d.csapak@proxmox.com>
On 30.10.20 15:02, Dominik Csapak wrote:
> this series extends the node/tasks api call with several new filters,
> and adds a new task panel to the ui that makes use of these filters
>
> the type selector will show all tasks in the current Proxmox.Utils object,
> so this will work best when [0] is applied
>
> 0: https://lists.proxmox.com/pipermail/pve-devel/2020-October/045730.html
>
> proxmox-widget-toolkit:
>
> Dominik Csapak (1):
> add form/TaskTypeSelector
>
> src/Makefile | 1 +
> src/form/TaskTypeSelector.js | 12 ++++++++++++
> 2 files changed, 13 insertions(+)
> create mode 100644 src/form/TaskTypeSelector.js
>
> proxmox-backup:
>
> Dominik Csapak (6):
> server/worker_task: add tasktype to return the api type of a taskstate
> api2/node/tasks: change limit behaviour when it is 0
> api2/node/tasks: add optional since/typefilter/statusfilter
> api2/status: remove list_task api call
> api2/node/tasks: add optional until filter
> ui: add panel/Tasks and use it for the node tasks
>
> src/api2/node/tasks.rs | 67 ++++++-
> src/api2/status.rs | 99 ----------
> src/server/worker_task.rs | 11 +-
> www/Dashboard.js | 3 +-
> www/Makefile | 1 +
> www/ServerAdministration.js | 2 +-
> www/dashboard/TaskSummary.js | 3 +-
> www/panel/Tasks.js | 362 +++++++++++++++++++++++++++++++++++
> 8 files changed, 438 insertions(+), 110 deletions(-)
> create mode 100644 www/panel/Tasks.js
>
applied remaining series, thanks!
Did some field reordering to use more of the extra vertical space instead of
shrinking the task grid to much for the filters.
Also, button icons, a clear trigger for task type, fieldLabel fixes and a
emptyText for clarity - just for the record.
prev parent reply other threads:[~2020-11-03 13:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 14:02 [pbs-devel] " Dominik Csapak
2020-10-30 14:02 ` [pbs-devel] [PATCH widget-toolkit 1/1] add form/TaskTypeSelector Dominik Csapak
2020-10-30 17:19 ` [pbs-devel] applied: " Thomas Lamprecht
2020-10-30 14:02 ` [pbs-devel] [PATCH proxmox-backup 1/6] server/worker_task: add tasktype to return the api type of a taskstate Dominik Csapak
2020-10-30 14:02 ` [pbs-devel] [PATCH proxmox-backup 2/6] api2/node/tasks: change limit behaviour when it is 0 Dominik Csapak
2020-10-30 14:02 ` [pbs-devel] [PATCH proxmox-backup 3/6] api2/node/tasks: add optional since/typefilter/statusfilter Dominik Csapak
2020-10-30 14:02 ` [pbs-devel] [PATCH proxmox-backup 4/6] api2/status: remove list_task api call Dominik Csapak
2020-10-30 14:02 ` [pbs-devel] [PATCH proxmox-backup 5/6] api2/node/tasks: add optional until filter Dominik Csapak
2020-10-30 14:02 ` [pbs-devel] [PATCH proxmox-backup 6/6] ui: add panel/Tasks and use it for the node tasks Dominik Csapak
2020-11-03 13:52 ` Thomas Lamprecht [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=353dbddf-c9b4-9b41-b585-85f006e9cfb7@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@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