Make Oscar agnostic of thumbnailing solution

Oscar really shouldn’t care how thumbnails are generated. It leads to trouble when integrating e.g. django CMS as they use easy-thumbnails. There’s also solutions like thumbor and resrc.it better suited for handling thumbnails when using remote storages like S3.

I’m imagining a backend-agnostic oscar_thumb template tag that is easy to customise. As far as I’m aware, the only advanced usage of the thumbnail tag is crop=centre for the gallery thumbs, which surely could be made to work somehow.

Questions remaining:

• Should we drop Sorl as a required dependency? That means PIL wouldn’t get installed by default, which makes the final environment lighter. But it probably doesn’t provide for a good out-of-the-box experience.

[bogh]

I’ve looked over @JostCrow implementation and I think it’s not a good idea to duplicate the templates. Give that there are quite a few. I was thinking a template tag that returns the thumbnail of the image and wraps both libraries and any future that wants to be used.

Allowing for a setting that will specify the THUMBNAIL_FUNCTION to be called and create and return the thumb of the image.

I will start working in this direction and I’m open to suggestions.

[sephii]

I started working on this here https://github.com/liip-forks/django-oscar/tree/agnostic-thumbnails