Although thumbnails are something *many* sites do, everyone have wildly different requirements, and therefore, different solutions. Two simple requirements that vary so much that makes impossible to have a "standard" for thumbnails:
- The API for making thumbnails. Is it a backend class? Is it a template tag? Is it a specially crafted URL with GET params, or maybe REST? - The storage for the thumbnails. Local files? S3 storage? Rackspace Cloud Files? Maybe a cache backend? Something weird? And how to invalidate cache images? Clean the cache if the original is gone? As such, IMO is too hard to ship something so big and so opinionated as a thumbnails solution on contrib. It's also so decoupled from Django internals (it should depend just on a File object, and maybe provide template tags) that it can live as a separate module just fine. Please consider Django aim is to be a framework, not a generic turn- key solution for making sites (although it's easy to get started). On Sep 16, 2:00 am, Yo-Yo Ma <baxterstock...@gmail.com> wrote: > Is there any plans to > incorporatehttp://github.com/SmileyChris/easy-thumbnails/ > into django.contrib? I have seen so many apps/libraries come into and > go out of existence (http://code.djangoproject.com/wiki/ThumbNailsfor > instance mentions sorl-thumbnails which is no longer being developed). > I just turned the key with easy-thumbnails and voila. It's like magic, > but not. It's easy enough to see what's going on behind the scenes. > > This is something that, with the help of the core and other > contributors, could be really great. It works for me as it it is, but > it may not work for a more "enterprise" application that uses S3, etc. > It might not be highly efficient (I wouldn't know). It might have bugs > that I just haven't noticed yet. I'm mentioning all of this because I > know somebody will say, "Why move it into Django if it's doing just > fine as a separate project?". After experiencing the bliss I thought > I'd drop a line here about it, and see what you guys thought. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
