public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: ''backup.cgi' - new icons - new order - query for delete / translation strings
Date: Tue, 04 Dec 2018 14:55:06 +0100	[thread overview]
Message-ID: <90a14944bd2ece5e9b36b54e1ee7db6b4a42471e.camel@ipfire.org> (raw)
In-Reply-To: <5CB0C534-EF45-4A45-8EFC-A4DEEB6AF937@rymes.com>

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

Hi Matthias,
and thanks for not giving up in this topic and for your hard work to
stay there actual also after one+ year. I do also think it is a good
idea to clean up the language files even there are not only some
doubles but also triples like e.g.

...
'delete' => 'Löschen',
...
'remove' => 'Löschen',
...
'fwdfw delete' => 'Löschen',
..

but also really a lot´s of unused ones. 

backup.cgi: It seems that this CGI is one of the older ones, a unified
design to the rest should give the WUI possibly more visual consistens
in my opinion but the order of the icons makes also more sense in that
way.

onclick: yes/no confirmation has been often ask for in the forum (it
s...s if you accidentially delete a VPN client or a backup) but as Tom
Rymes said it already, even we have already (nearly) all CGIs patched,
some of them would probably not need a deletion confirmation, a
question arises then which one doesn´t ?


Nice project contribution from you Matthias, thanks again.

Best,

Erik


Am Sonntag, den 25.11.2018, 08:30 -0500 schrieb Tom Rymes:
> Matthias,
> 
> I can’t comment on everything, but I do know that I have consistently
> been confused by the icons on the backup page.
> 
> Confirmation dialogs seem good, so long as we don’t go overboard and
> ask “are you sure” for every tiny action.
> 
> Tom
> 
> > On Nov 24, 2018, at 4:39 PM, Matthias Fischer <
> > matthias.fischer(a)ipfire.org> wrote:
> > 
> > Hi,
> > 
> > Something similar has been posted before ([PATCH] Cosmetics: New
> > icons
> > for backup.cgi), but unfortunately the discussion was not continued
> > for
> > very long.
> > 
> > Triggered by:
> > 
> > https://forum.ipfire.org/viewtopic.php?f=17&t=21372
> > 
> > and
> > 
> > https://forum.ipfire.org/viewtopic.php?f=17&t=21882
> > 
> > I'd like to know whether there is any interest in developing this
> > any
> > further. In the meantime, patches were built for 'backup.cgi' which
> > not
> > only update the icons and their order of precedence for better
> > readability and usability. In an additional step, the 'delete'
> > icons got
> > 'onclick'-confirmation boxes (by Erik!) to prevent accidental
> > deletions.
> > 
> > Another step could be to add this confirmation to other CGIs. This
> > additional query could prevent some trouble in the future as it
> > happened
> > to the original poster of the second link above. He accidentally
> > deleted
> > an OVPN client. No query... I'm already testing this functionality
> > in
> > other contexts (e.g., firewall rules, dhcp, hosts) and it works.
> > 
> > And the last question: each current lang file contains up to ~600
> > unused
> > translation strings. These are summing up to about 5000 strings
> > which
> > are not used or duplicates and could be deleted. Current size of
> > all
> > lang files is 1.2MB - we actually need about 900KB. A current patch
> > can
> > be found here:
> > 
> > 
https://git.ipfire.org/?p=people/ummeegge/ipfire-2.x.git;a=commit;h=acbf3208e4a0d61c138d38326079a29b97545007
> > 
> > At the beginning of this year I built some patches for these unused
> > strings and some other corrections
> > (https://patchwork.ipfire.org/patch/1605/) but sadly got no
> > reaction at
> > all. Is there any interest, should we re-edit the unused
> > translations?
> > 
> > What do you think? Opinions and comments are welcome...
> > 
> > Best,
> > Matthias


      reply	other threads:[~2018-12-04 13:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-24 21:38 Matthias Fischer
2018-11-25 13:30 ` Tom Rymes
2018-12-04 13:55   ` ummeegge [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=90a14944bd2ece5e9b36b54e1ee7db6b4a42471e.camel@ipfire.org \
    --to=ummeegge@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