I downloaded the patch and got it to work. I have a couple of observations based on usage.
- If we continue to use the format "150x200" to specify the size, we may want to do a string.lower() on the input. I originally had a capital X and couldn't figure out what the problem was. Yeah, it's a stupid mistake on my part but still.... - I'm a little fuzzy on the different methods and how they treat size constraints. I understand if I set the width and leave height blank, it should automatically calculate it once the thumb is created. I would also expect that if I put in both, it's going to scale it and lose the original aspect ratio. In other words, I'd like to see some thing like: picture|thumbnail"width=75" which would create a picture with the same aspect ratio of width to height. If I entered picture|thumbnail"width=75 height=25" It should force the image to that size (I think that's what squish does). I hope this makes sense. I think the by product of making this semantic change is that one tag would do thumbnail and crop. Otherwise it all appeared to work well for me. Oh yeah, upon thinking more about my comment on caching the image, I think you're probably right. We should leave that in the category of serving static media. -Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
