Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Image File Compression #2786

Merged
merged 1 commit into from
Apr 12, 2019
Merged

Conversation

Peppernrino
Copy link
Contributor

Ran a series of lossless compression algorithms to make the images smaller. Total reduction of ~13MB.

Ran a series of lossless compression algorithms to make the images smaller. Total reduction of ~13MB.
@CharlieFenton
Copy link
Contributor

Is there any reason to even keep clientgui/res/templates/icons and clientgui/res/templates/skins in the repository? I don't think they are used anywhere.

@CharlieFenton
Copy link
Contributor

Are you certain that files such as PNG, TIFF BMP, etc. are still properly displayed on all relevant platforms after this compression?

@Peppernrino
Copy link
Contributor Author

Peppernrino commented Oct 30, 2018

If anything can be removed entirely, I'm all for it.

As for the other files displaying properly, I don't see why they wouldn't. They're the same pictures, just smaller. Unless something is calling the images by their SHA hashes, we should be good. :)

There were some files that didn't display at all in Photo Viewer, or Github Desktop untiI had done the optimizations... in client/os2... the .ico files.

@CharlieFenton
Copy link
Contributor

My question was directed primarily to @romw and @davidpanderson, because they seem to be artwork which was used to create the images tat are actually used, but they also may be obsolete or at least no longe needed:

Is there any reason to even keep clientgui/res/templates/icons and clientgui/res/templates/skins in the repository? I don't think they are used anywhere.

@Peppernrino
Copy link
Contributor Author

Peppernrino commented Oct 30, 2018

Ah! Pardon me, friend. Just anxious to contribute to something big and useful. Watching the pot boil. lol :D

On that same note, I'm going to try my hand optimizing the Pixmap (.xpm) files as well. The program I used to optimize it also stripped the BOINC header information... but it seems there are some more efficient maths that could be pursued within.

@TheAspens
Copy link
Member

@Peppernrino - which tool did you use for the compression and what settings?

@Peppernrino
Copy link
Contributor Author

Peppernrino commented Nov 9, 2018

Example here: https://pastebin.com/MTtcVck2 :D

Applicable tools vary for each file type, but that's what was run on a .png.

@Peppernrino
Copy link
Contributor Author

Ready to go. The other gentleman scrapped his work. :)

@Rytiss
Copy link
Contributor

Rytiss commented Jan 15, 2019

I had the most concern about JPGs, but they don't seem to show any extra conversion artifacts. I also checked a somewhat random sample of files on Windows 10 and all seem to be displayed correctly using standard Windows image viewer.

As for removing unused assets, that should not block the merge of this commit. An issue should be raised and somebody can review the files later.

@lfield
Copy link
Contributor

lfield commented Apr 11, 2019

I looked at a random selection of images and they seem fine to me. Any objection to merging?

@CharlieFenton
Copy link
Contributor

I have no objection

@lfield lfield merged commit 18aa95e into BOINC:master Apr 12, 2019
@AenBleidd AenBleidd added this to the Server Release 1.2.0 milestone Aug 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants