From: Jon Murphy <jcmurphy26@gmail.com>
To: development@lists.ipfire.org
Subject: Re: [PATCH 0/3] Help for GUI
Date: Sat, 16 May 2020 11:10:59 -0500 [thread overview]
Message-ID: <C3C682C8-0A78-4352-8802-BF19E83CEA92@gmail.com> (raw)
In-Reply-To: <mailman.1.1589630401.3663.development@lists.ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2537 bytes --]
Oops… maybe my bad?
>
> ------------------------------
>
> Message: 3
> Date: Sat, 16 May 2020 10:35:00 +0100
> From: Michael Tremer <michael.tremer(a)ipfire.org>
> To: Tim FitzGeorge <ipfr(a)tfitzgeorge.me.uk>
> Cc: development(a)lists.ipfire.org
> Subject: Re: [PATCH 0/3] Help for GUI
> Message-ID: <6390F8AE-998D-489E-A983-1A875E2761F2(a)ipfire.org>
> Content-Type: text/plain; charset=utf-8
>
> Hi Tim,
>
> Thank you very much for submitting these patches.
>
> I am afraid that I must say that I oppose these changes.
>
> This has recently been discussed on the community portal and although I still have not made my mind up entirely, I think this not helpful to anyone:
>
> * We do not have documentation for everything for a start
> * There is never this ?just read one sentence and you suddenly will be an expert? thing this kind of promotes
>
> Should we not rather link the wiki somewhere in the footer and encourage people to start reading the whole thing from the start before they do something?
>
> What is your rationale to implementing this?
>
> Best,
> -Michael
>
>> On 15 May 2020, at 22:39, Tim FitzGeorge <ipfr(a)tfitzgeorge.me.uk> wrote:
>>
>> Add per-page help link to GUI.
>> The link is extracted from the menu file and added to the menu.
>> Currently only implemented for 'ipfire' and 'ipfire-rounded' themes.
>>
>> Tim FitzGeorge (3):
>> Help for GUI - ipfire theme code
>> Help for GUI - Help links
>> Help for GUI - help link style
>>
>> config/menu/10-system.menu | 11 +++++++
>> config/menu/20-status.menu | 13 ++++++++
>> config/menu/30-network.menu | 20 +++++++++--
>> config/menu/40-services.menu | 6 ++++
>> config/menu/50-firewall.menu | 8 ++++-
>> config/menu/60-ipfire.menu | 1 +
>> config/menu/70-log.menu | 33 ++++++++++++-------
>> config/menu/EX-apcupsd.menu | 1 +
>> config/menu/EX-guardian.menu | 1 +
>> config/menu/EX-mpfire.menu | 1 +
>> config/menu/EX-samba.menu | 1 +
>> config/menu/EX-tor.menu | 1 +
>> config/menu/EX-wlanap.menu | 1 +
>> html/html/themes/ipfire/include/css/style.css | 8 +++++
>> html/html/themes/ipfire/include/functions.pl | 19 +++++++++--
>> 15 files changed, 107 insertions(+), 18 deletions(-)
>>
>> --
>> 2.26.1
>>
>
>
next parent reply other threads:[~2020-05-16 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1589630401.3663.development@lists.ipfire.org>
2020-05-16 16:10 ` Jon Murphy [this message]
[not found] <mailman.125.1590157028.797.development@lists.ipfire.org>
2020-06-10 0:05 ` Jon Murphy
[not found] <851be8bf-9193-3c8a-1802-94a54b70909f@tfitzgeorge.me.uk>
2020-05-22 13:22 ` Michael Tremer
[not found] <04413F0C-96CD-4213-AC55-8012E649FB64@gmail.com>
2020-05-21 18:51 ` Jonatan Schlag
2020-05-22 13:19 ` Michael Tremer
[not found] <F683B9F1-464A-44C5-9E5B-13F91CAEE77F@gmail.com>
2020-05-19 20:45 ` Tim FitzGeorge
2020-05-15 21:39 Tim FitzGeorge
2020-05-16 9:35 ` Michael Tremer
2020-05-18 20:18 ` Tim FitzGeorge
2020-05-22 13:07 ` Michael Tremer
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=C3C682C8-0A78-4352-8802-BF19E83CEA92@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