Comment 17 for bug 1550706

Still not trying to rain on the part here... :-)

I'd like to make it work. But having images buried inside an executable is not a good idea when it comes to interoperating with tools such as the thumbnailer. Personally, I don't think the thumbnailer is a good fit for this.

Is it possible to *not* bury the images that way? If so, and they are proper files, the thumbnailer will instantly do what you want.

If all that is needed is scaling, the thumbnailer may well be overkill though. For example, you could ship different assets for different resolutions (that's the iOS approach), or you could scale the image once and keep it in your own persistent-cache-cpp instance. The API for that is child's play, so that might be viable.

For an image cache, I'd seriously suggest to look at persistent-cache-cpp. It underpins the thumbnailer, and it works really well. Please ping me if you have questions about cache coherency, dealing with updated images, etc. I'm happy to help. But, so far, it looks to me the the thumbnailer is far too heavy-weight a solution for what you need, and persistent-cache-cpp would be a better fit.