2012-02-27, 23:36
v1.2.0
- added ability to use local or remote images
- added priority image control to use local first, remote first, or both
- added option to restrict downloads to 16:9 images
- added option to have slideshow refresh after every image download or after x seconds
- added option for override folder that will be showed instead of artists images
- updated logic to refresh images after all are downloaded
- fixed potential script crash if remote sites unavailable
- experimental support for limiting size of cache folder
This should be showing up for folks in the next few days or so.
The last thing I added before the pull request was experimental support for limiting the size of the cache. I say experimental because while it works without a hitch on OSX (and probably Linux given they are at their very core Unix variants), on Windows I ran into some weird problems I had to error catch around. Specifically Windows (at least on my machine) sometimes only mostly deletes directories (it's like being mostly dead for you Princess Bride fans). What is left there still shows up in the directory listing but is inaccessible. After adding the error catching, I ran this for about five hours on my Windows machine without any issues, but I still decided to mark the feature experimental now.
The cache manager only attempts to limit the cache in the addon data directory. The smallest size limit you can set is 256mb and the largest is 4gb (obviously if you don't turn on cache management, you are limited only by your disk space). I was trying to balance disk use with API use for the remote sites, and I think even 256mb still strikes that balance. If you can't spare 256mb on your drive, you really need to think about getting a new drive. :p
The cache limit you set is sort of an ideal rather than an absolute. There are two use cases where your cache will get larger than the maximum.
1- The cache manager will not delete the only folder in the cache, so if you have an artist that has lots of artwork (I mean *lots*) and that is the only artist in the cache, the cache could be larger than the max set. If you find an artist with more than 256mb of downloaded images, please let us know. I'd like to see that one.
2- The cache manager trims the cache after downloading the images for the currently playing artist. So if you are close to the max, the current artist could push you over the top for a brief moment. Once all the current images are downloaded the cache will drop below the max size.
If you decide to use both local and remote images, you are own your own for space management. There is no way I'm going to start mucking around in a directory that has some script managed content and some user managed content.
Baring bugs or new feature requests, the only thing I'm working on is to get the script to take an artist as an argument so that other plugins can use this plugin to display music slideshows (i.e. the new Squeezebox plugin). We're making baby steps on that front.
- added ability to use local or remote images
- added priority image control to use local first, remote first, or both
- added option to restrict downloads to 16:9 images
- added option to have slideshow refresh after every image download or after x seconds
- added option for override folder that will be showed instead of artists images
- updated logic to refresh images after all are downloaded
- fixed potential script crash if remote sites unavailable
- experimental support for limiting size of cache folder
This should be showing up for folks in the next few days or so.
The last thing I added before the pull request was experimental support for limiting the size of the cache. I say experimental because while it works without a hitch on OSX (and probably Linux given they are at their very core Unix variants), on Windows I ran into some weird problems I had to error catch around. Specifically Windows (at least on my machine) sometimes only mostly deletes directories (it's like being mostly dead for you Princess Bride fans). What is left there still shows up in the directory listing but is inaccessible. After adding the error catching, I ran this for about five hours on my Windows machine without any issues, but I still decided to mark the feature experimental now.
The cache manager only attempts to limit the cache in the addon data directory. The smallest size limit you can set is 256mb and the largest is 4gb (obviously if you don't turn on cache management, you are limited only by your disk space). I was trying to balance disk use with API use for the remote sites, and I think even 256mb still strikes that balance. If you can't spare 256mb on your drive, you really need to think about getting a new drive. :p
The cache limit you set is sort of an ideal rather than an absolute. There are two use cases where your cache will get larger than the maximum.
1- The cache manager will not delete the only folder in the cache, so if you have an artist that has lots of artwork (I mean *lots*) and that is the only artist in the cache, the cache could be larger than the max set. If you find an artist with more than 256mb of downloaded images, please let us know. I'd like to see that one.
2- The cache manager trims the cache after downloading the images for the currently playing artist. So if you are close to the max, the current artist could push you over the top for a brief moment. Once all the current images are downloaded the cache will drop below the max size.
If you decide to use both local and remote images, you are own your own for space management. There is no way I'm going to start mucking around in a directory that has some script managed content and some user managed content.
Baring bugs or new feature requests, the only thing I'm working on is to get the script to take an artist as an argument so that other plugins can use this plugin to display music slideshows (i.e. the new Squeezebox plugin). We're making baby steps on that front.
