From: Jon Murphy <jcmurphy26@gmail.com>
To: development@lists.ipfire.org
Subject: Re: [V2] Backup.cgi: Rework and altering of functionalities and GUI for better usability
Date: Sat, 22 May 2021 11:53:42 -0500 [thread overview]
Message-ID: <4DE168F2-C774-4B1F-BBAA-372BED9C35C9@gmail.com> (raw)
In-Reply-To: <167e8e93-3c40-f85c-9cb5-a552ca1ff9d5@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]
I like it! "make it so"
Jon
> On May 22, 2021, at 9:53 AM, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Still based on https://bugzilla.ipfire.org/show_bug.cgi?id=12588
>
> Hi,
>
> in the meantime I worked on this - a bit - again. Currently, this CGI is
> running here under Core 156 with no seen problems.
>
> I've made several changes and adjustments.
>
> First:
> - I kept the icons - buttons didn't look as I hoped they would. ;-)
>
> - I kept the old icon order "Download - Delete - Save".
>
> Changelog:
> - Cleaned up the code a bit, some if-queries were unnessecary (if
> ($cgiparams{'ACTION'} eq...).
>
> - Therefore, some lang strings became obsolete ('downloadaddon' and
> 'downloadiso'.
>
> - Separated the ISO files from the IPF files for better overview.
>
> - Added query for deleting a backup file (onclick=\"return confirm...).
>
> - Added 'onclick' feature => deleting a file must be acknowledged.
>
> Biggest change:
> - Added tables - as MT mentioned.
>
> Details can be seen in the attached screenshots.
>
> Thoughts? Opinions? I'd like to get some feedback before pushing this... ;-)
>
> Best,
> Matthias
>
> <2021-05-22_backup.cgi.png><2021-05-22_backup.cgi_onclick.png>
next parent reply other threads:[~2021-05-22 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <167e8e93-3c40-f85c-9cb5-a552ca1ff9d5@ipfire.org>
2021-05-22 16:53 ` Jon Murphy [this message]
2021-05-25 10:34 ` Michael Tremer
2021-05-26 11:01 ` Adolf Belka
2021-05-26 15:32 ` Matthias Fischer
2021-05-26 15:53 ` Adolf Belka
2021-05-26 15:58 ` Leo Hofmann
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=4DE168F2-C774-4B1F-BBAA-372BED9C35C9@gmail.com \
--to=jcmurphy26@gmail.com \
--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