| | 1 | = Discussion about Thumbnail Contribution for Django = |
| | 2 | |
| | 3 | == Problem == |
| | 4 | The majority of applications that have images, probably use thumbnails in some capacity. There is no standard thumbnail capability in Django but there are a couple of different options out there that people have created. This page is an attempt to gather them in one place and discuss the best strategy for integrating one in Django. |
| | 5 | |
| | 6 | The original thread discussing this issue is here - |
| | 7 | [http://groups.google.com/group/django-developers/browse_thread/thread/322ec3bbb1a23ac1 Google Discussion] |
| | 8 | |
| | 9 | == Current Implementations == |
| | 10 | |
| | 11 | * Nesh's thumbnail is probably the most robust - [http://code.google.com/p/django-utils/wiki/Thumbnail Nesh's Thumbnail] |
| | 12 | * Here's a more simple filter from Django snippets - [http://www.djangosnippets.org/snippets/192/ Simple filter] |
| | 13 | |
| | 14 | == Design Considerations == |
| | 15 | Whichever solution is considered should have the following features: |
| | 16 | |
| | 17 | * Capability to define arbitrary thumbnail sizes in templates |
| | 18 | * Caching of the files to disk and possibly to memory |
| | 19 | |
| | 20 | Some key questions: |
| | 21 | * Do we want to create a new field or just expand the existing image field? |
| | 22 | |
| | 23 | |
| | 24 | == Other Notes == |