Comment 18 for bug 1550706

* Sure it is possible to not ship artwork in a qrc. However, that requires the developer to fiddle with the apparmor confined paths and afaict, there's no QML-only way to do so. Besides, as I said before, the default in our sdk templates is to put things in a qrc to ease up development.

* I agree that the persistent-cache-cpp is childplay for people like us, again there's no qml api for it so requires people to dive into C++ which apparently many refuse to do. So the way forward would be to create another QML image provider pretty much in the same way as the thumbnailer does, except scaling and caching things only. This is probably what I'd do in case we decide this out of scope for the thumbnailer.

* Shipping different sized assets, sure, possible too. But you probably won't ever be able to ship perfectly sized assets for every screen we run on, at least not when keeping the package to a reasonable size. I hoped we could be more clever in this regard than going the easy way.

In any case. I totally understand if we decide this is out of scope for the thumbnailer. Still a bit wondering why it does implement the scaling of local images use case then at all and does not just media artwork matching/fetching alone then.