On 4/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > 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.... Easy fix and good idea.
> > - 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" You can't leave the width or height blank. "scale" sizes the image down proportionally until it fits inside the given dimensions so the thumbnail images may differ in their dimensions (they'll either have the width or height - would you really want an image to be scaled down to 75px width but still be 10,000px high?) "crop" cuts off parts of the image to make it take up exactly the width and height you specify (but without skewing the image ratio like "squash" does) So we can't combine scale and crop, because they do different things. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
