You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
One can save quite some amount of bandwidth when all images are optimised (losslessly).
a) When there is a "best practices" document (or something like that) for your Icinga-Web developers, than please add that they should process PNGs and JPEGs with:
jpegoptim
optipng -o 7
in the future.
b) For the current PNGs/JPGs I've already did this.
Attached are two patches.
Migrate old filter to new ones
Implements phing build task which uses old filter
structs in state of custom cronks and convert it
into new format (refs #3260). So filter can be
used beyond version.
fixes #3981
The text was updated successfully, but these errors were encountered:
This issue has been migrated from Redmine: https://dev.icinga.com/issues/3260
Created by calestyo on 2012-10-08 01:48:36 +00:00
Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2015-05-18 12:17:37 +00:00 (in Redmine)
Hi.
This is analogous to bug #3259.
One can save quite some amount of bandwidth when all images are optimised (losslessly).
a) When there is a "best practices" document (or something like that) for your Icinga-Web developers, than please add that they should process PNGs and JPEGs with:
jpegoptim
optipng -o 7
in the future.
b) For the current PNGs/JPGs I've already did this.
Attached are two patches.
Thanks,
Chris.
Attachments
Changesets
2013-04-18 13:53:24 +00:00 by mhein e3e0433
The text was updated successfully, but these errors were encountered: