Archived from the Transloadit support forum. Originally posted on October 30, 2010; details may be outdated, see our docs for current behavior. Original thread
My users should be able to create their own thumbnail by defining a crop area from the image they’ve uploaded. I wonder where Transloadit comes into play in this workflow. This is the scenario:
User uploads a high resolution image.
Transloadit uploads and resizes the image so it fits in a web page.
Transloadit stores the image on S3.
The user creates a thumbnail from the image (that is being pulled from S3) with a JQuery crop tool.
The thumbnail is stored on S3.
This results in three files:
1. original file (high resolution)
2. resized file (web optimized)
3. thumbnail
I assume that Transloadit will need to re-upload the image in order to create a thumbnail from it. Is that correct, or can I tell Transloadit to use an image already on S3?
My users should be able to create their own thumbnail by defining a crop area from the image they’ve uploaded.
We don’t support this right now, but I’d love to add support for that for you. What’s the timeline for you to implement the cropping so I can figure out how to prioritize it in our tasklist?
I assume that Transloadit will need to re-upload the image in order to create a thumbnail from it. Is that correct, or can I tell Transloadit to use an image already on S3?
You can use our '/http/import' robot to tell transloadit to use a file from a given url, so no need to re-upload.
Anyway, let me know if you have further questions about this!
Note: After cropping I store the x, y, width and height variables in the user’s table so I can always re-crop the image later (e.g. for when my site requires a different thumbnail size). So it’s important to return those variables as well.
To be clear, my setup actually first crops and then re-sizes the cropped image to a thumbnail.
I’ll probably release my new site within a month or so.
I’m confused, you are saying you already have the cropper working with transloadit? What I was trying to say in my previous email was that our /image/resize robot does not yet support the “x, y, width, height” cropping.
Oops, there is a misunderstanding here, I thought you were going to implement the JQuery cropper. I have the JQuery cropper running and it could use /http/import but it would fail creating the crop using x, y, width and height.
So yes, it would be great if you could extend the /image/resize robot to support this.
Alright, I’ve placed cropping high enough on our todo list should it should be implemented soon. I’m closing this ticket for now, but I’ll ping you when it’s ready.
Feel free to ask me anything else if you have more questions!