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

Resizing and Caching #2

Open
dpk3062 opened this issue Mar 16, 2014 · 0 comments
Open

Resizing and Caching #2

dpk3062 opened this issue Mar 16, 2014 · 0 comments

Comments

@dpk3062
Copy link
Contributor

dpk3062 commented Mar 16, 2014

It takes the pi roughly 15 seconds to resize a photo, meaning each image is displayed for at least 15 seconds its first time no matter how fast the slide show is set to run.

Instead of only caching resized images in memory, they should be saved to the disk as well. If a cache hit misses, it should check a directory to see if a resized version of the photo exists.

When an image is resized, it should save a copy of itself.
When an image is to be read in, the disk cache should be checked and the resized version loaded instead. Resized versions should not be re-resized. Only the original image should be adjusted.

The cache folder could contain: imageName-800-by-600.jpg or 800-by-600-imageName.jpg. I'm not sure which is better. One lets you easily order by size while the former lets you order by image duplicates.

@dpk3062 dpk3062 modified the milestone: Version 1 Mar 16, 2014
@dpk3062 dpk3062 modified the milestones: Open House, Version 1 Apr 11, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant