A helpful GLoSS user, Bob Bristow, passes along the following information about one way to configure your Gallery to serve you resized images instead of the originals (the Gallery Remote Protocol that GLoSS uses doesn't appear to natively allow GLoSS to request resized images, hence this workaround):
I've experienced this on one machine which also had Google Desktop installed. It seems that the Google Desktop indexing service (or one of the other constituent parts of Google Desktop) is interfering with the ability of GLoSS to retrieve images successfully from it's cache folder. If you are also experiencing this issue, I suggest you try one of the suggestions below, since I'm currently completely unsure how to handle this situation inside GLoSS:
Secondary Caching was implemented in response to a request from a happy user to provide the ability for multiple instances of GLoSS to partially share cache folders. You can now specify a secondary cache folder for GLoSS to check for local versions of Gallery images before GLoSS downloads the image from your Gallery. This is expected to be useful in small home networks, especially with laptops, etc.
It works as follows:
That's great, thanks! There are a couple of things I should point out:
GLoSS started off as a pet project for me so that I could "push" images on to my not-particularly-computer-literate family's PCs (most of whom live in the UK while I live in New Zealand). I also have a full time job. Therefore, I'm mainly motivated to add functionality to GLoSS which seems useful to me with my Gallery. It may also be that I don't have my Gallery configured in such a way that's easy for me to test the suggested functionality against.
Having said all that, I've been really grateful for the feedback that I've received from people who've made suggestions and tested GLoSS for me, and have implemented quite a few previous suggestions as a result.
Also, while I'm grateful for any PayPal donations that users of GLoSS are kind enough to make, there aren't enough to cover my hosting bills, let alone encourage me to spend more of my precious free time adding unlimited bells and whistles to GLoSS! Please don't let that stop you making donations and/or suggestions; it's just that I may not be able to commit to adding a particular feature to GLoSS.
The auto-purge functionality is designed to remove images in your cache, which no longer exist in your Gallery.
If you have enabled the auto-purge feature, GLoSS follows this process:
One possible reason for this is that if the Quota module is activated in your Gallery, the image(s) you're trying to upload may break the quota limit set for your account. Unfortunately, Gallery's Remote Protocol always reports that it has successfully uploaded the image(s). This is an issue with the Remote Protocol rather than GLoSS. If you want to encourage the Gallery developers to fix this bug, you can vote for it over at the Gallery site here.
GLoSS has been successfully tested with JPEGs and PNGs. In testing, it appears that for some other image types (e.g. TIFF) uploaded to Gallery, Gallery by default displays JPEG versions of these in your browser instead. Therefore GLoSS will also support these types of image, since the Image Block will serve JPEGs instead.
The short answer is Yes.
GLoSS stores all images from your Gallery in it's local cache folder on your PC. When GLoSS is offline (either because you've explicitly set GLoSS to Offline mode or because you're not currently connected to the internet), it will use random images from the local cache folder on your PC.
Therefore, if you add more images to this folder, and set GLoSS to Offline, these "non-Gallery" images will be available for random display by GLoSS too.
However, when GLoSS is in Online mode and you are connected to the internet, it will only display cached images that have been downloaded from your Gallery.
NOTE: If you have the auto-purge functionality in GLoSS enabled, you may like to consider turning it off, as these manually added images will be elegible to be purged from the local cache folder as determined by your auto-purge settings.
Not at the minute, and there is unlikely to be so in the future at this stage. GLoSS is developed using Borland Delphi 2006, and as such is really only aimed currently at 32-bit Windows operating systems such as Windows 2000 and XP. Use of techniques such as alpha-blending also mean that current versions of GLoSS will probably not work correctly on Windows 98 etc. I only test GLoSS on Windows XP, although I'm aware of users happily using it on Windows 2000 at least.
Absolutely not.
GLoSS exists simply to download and display images on your computer from the Gallery2 installation that you configure it to use. Therefore GLoSS will only use the internet to communicate with webservers that you tell it to. The single exception to this is the simple version check that GLoSS performs on startup, when it will check the latest available version number of GLoSS from the GLoSS website at http://gloss.ildica.com/. GLoSS does not send any identifiable information to the GLoSS website during this process; it simply asks what the latest available version number is. GLoSS is purely supported by PayPal donations.
Hold down the Ctrl key on your keyboard while you drag the borders and/or surface of the widget as desired.