From: Leo Hofmann <hofmann@leo-andres.de>
To: development@lists.ipfire.org
Subject: Re: [PATCH 1/3] rrdimage: Add scripts for new graph display method
Date: Thu, 01 Apr 2021 15:36:44 +0200 [thread overview]
Message-ID: <bec50845-bdf5-55d3-aa62-f86410e4b77a@leo-andres.de> (raw)
In-Reply-To: <20210401133516.1058-1-hofmann@leo-andres.de>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
Hi all,
this series of patches is a follow-up to this discussion: https://lists.ipfire.org/pipermail/development/2021-March/009523.html
I decided to write a new CGI which handles the graph image generation (png). This allowed me to add new features and remove a lot of uneccessary parameter handling from the other CGIs.
I think this is in presentable form now. But there are still some issues I'd like to hear your opinion on:
- Because I have collected all the graph functions from the CGIs, there is now a very long if-elseif chain in getrrdimage.cgi. I tried my best to keep this as readable as possible. But I'd be happy to rewrite that if someone knows a better method.
- My test system doesn't have any hardware sensors or IPsec connections. I'm pretty sure that these graphs work but I can't test them.
- getrrdimage.cgi redirects graphs it can't generate to ensure compatibility with addons. Is that necessary?
Happy holidays!
Leo
next prev parent reply other threads:[~2021-04-01 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 13:35 Leo-Andres Hofmann
2021-04-01 13:35 ` [PATCH 2/3] rrdimage: Add CSS and Javascript to ipfire theme Leo-Andres Hofmann
2021-04-01 13:35 ` [PATCH 3/3] rrdimage: Switch graphs.pl to the new graph scripts Leo-Andres Hofmann
2021-04-01 13:36 ` Leo Hofmann [this message]
2021-04-01 13:58 ` Aw: Re: [PATCH 1/3] rrdimage: Add scripts for new graph display method Bernhard Bitsch
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=bec50845-bdf5-55d3-aa62-f86410e4b77a@leo-andres.de \
--to=hofmann@leo-andres.de \
--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