public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Backup: Rework and altering of functionalities and GUI for better usability
Date: Mon, 22 Mar 2021 11:36:15 +0000	[thread overview]
Message-ID: <572900B7-43E8-4F0E-8E39-286EB70FD537@ipfire.org> (raw)
In-Reply-To: <87635bb9-1376-b674-11fa-699f014131e4@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2020 bytes --]

Hello,

> On 21 Mar 2021, at 18:25, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Based on https://bugzilla.ipfire.org/show_bug.cgi?id=12588
> 
> Hi,
> 
> in the meantime I worked on this - a bit.

Very good idea. This page is quite essential, but the design is quite complicated and difficult to use.

> I've made several changes and adjustments which could be implemented one
> by one - if they are wanted/accepted:
> 
> - Changed icons to buttons => better readability.

Yes. I am not sure whether “Backup” is a good choice, because it could be interpreted as a noun. Maybe “Backup Now” or “Update Backup” would be a better choice. Does anybody have any ideas?

> - For buttons to work, I added two lang strings for button labeling.

No problem here.

> - Cleaned up the code a bit, some if-queries were unnessecary (if
> ($cgiparams{'ACTION'} eq...).
> 
> - Changed the order of the (Addon-)buttons to "Download - Save - Delete"
> (old: Download was in the middle).

What is the rationale here?

Why is this order better?

> - Marked IPF-files bold => better readability (I already sent this in
> one day: => https://patchwork.ipfire.org/patch/3124/).

Can we not have a proper table here? Like this:

| Package    | Last Backup      | Size |                              |
| wio        | 2021-03-22 11:31 | 8 kB | [Download] [Backup] [Delete] |

> - Added query for deleting a backup file (onclick=\"return confirm...).

Very good idea, too.

Can we make this a function that we can add to various other places, too? Like firewall rules?

> Details in the attached screenshot.
> 
> Proposed ToDo - as a start: Alter the info text for restoring to make
> clear that only the addon *configs* are restored, not the addons themselves.

Yes.

> Thoughts? Opinions?

Very good ideas. Please keep them all in individual patches so that they can be reviewed one by one :)

-Michael

> 
> Best,
> Matthias
> <backup-cgi-tuned.png>


       reply	other threads:[~2021-03-22 11:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87635bb9-1376-b674-11fa-699f014131e4@ipfire.org>
2021-03-22 11:36 ` Michael Tremer [this message]
2021-03-22 17:30   ` Matthias Fischer
     [not found] <0BEB5DBD-425A-491C-8D62-547244AF45C0@gmail.com>
2021-03-23  9:10 ` Adolf Belka
2021-04-14 20:48   ` Jon Murphy
2021-04-15  8:58     ` Matthias Fischer
2021-04-15 17:38       ` Jon Murphy
     [not found] <9ff0a54e-b60f-e552-f92c-fb6f52ba351f@ipfire.org>
2021-04-18 13:54 ` Adolf Belka
2021-04-18 14:19   ` Matthias Fischer

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=572900B7-43E8-4F0E-8E39-286EB70FD537@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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