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

Cache images locally #4

Closed
jsayol opened this issue Apr 11, 2015 · 0 comments
Closed

Cache images locally #4

jsayol opened this issue Apr 11, 2015 · 0 comments
Assignees

Comments

@jsayol
Copy link
Owner

jsayol commented Apr 11, 2015

NW.js already has some sort of caching built in but it seems to be very unreliable. Every so often all the images get fetched again whenever they are displayed, which might become a problem if the user is on a slow/metered connection or just offline.

As the default behavior, instead of pointing to the tmdb site to show the images the app should cache them locally first and show that copy.

Additionally, add these in the settings:

  • Option to disable the cache and just show the images "live".
  • Option t empty (delete) the current cache. Ideally, it should let you choose either all of it or just that of a single collection.
@jsayol jsayol self-assigned this Apr 11, 2015
@jsayol jsayol closed this as completed Dec 2, 2016
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

No branches or pull requests

1 participant