A simple CommonJS module to cache images a little less temporarily, and configurable
To.ImageCache CommonJS module to your project. Either download this project, or install using
gittio install To.ImageCache
Follow regular steps to include it in your project
In classic go to the
Resources folder, for Alloy go to the
lib directory of your project, then run the following command
npm install to.imagecache
Note: if your app doesn't have
node_modules yet, run
npm init first!
IMPORTANT: Version 1.0 is not backwards compatible with previous versions. Name has changed to lowercase for NPM support
The configuration is simple: No configuration is needed, unless you want to change something.
All current properties available shown below
The config can be changed at all times, between different files so support multiple folders, expiration times and file specfic backup properties. You only have to pass what you want to change from now on. No need to pass all config properties
If you want to make a copy of the config, so you can restore it later, use the getter
var config = ;
All available images will be stored in Properties
There is, however, no need to call this list manually unless you really want to. Best to use build in functionality
There are 2 methods to use the module.
Only call the module when the image is needed, it will then, return a blob of the image while you wait.
Note: This might cause delays in your app and is only recommended for smaller images
var blob = ;
This will cache the image the first time it is called, and the next time you request this same file it will return the same blob, but this time stored locally
Pre-cache images before they are needed
This method is preferred for bigger images, as this can happen in the background
This function will NOT return a blob, but will cache the file using
Aditonally, you can add a timeout and callback function:
You want, of course, to clear the cache when needed. This is NOT done automatically.
The best function to call is
This function will remove all files older than the expired time.
You can also clear all cache
This will remove all cached files regardless of expired time.
You can also remove a single file by URL:
This will also NOT take expiry time in consideration
If you know the filename (which is internally generated, so you probably won't), you can remove by filename too
You can fetch the entire cache size, in bytes, from the module. This could, for example, be used to display users so they can be aware how much cache is present, and you could give the users the ability to remove cache manually
You can also, at a later point, update the config. Expire time is per-file, and stored per-file. So changing it later will not update the currently stored files. Might be usefull for different expiry times.
Also the folder can be changed multiple times. Folders are also stored per file, so changable all the time.