Before I start I need to preface this feature request with a note that I am not expecting this to be added as it goes beyond the present intent of the module. However, I think this would be a "killer feature" that would get a lot of use an attention.
When looking through the jQuery interface plugins I noticed resizable image cropping. This interface allows users to quickly select a crop are a via a drag and drop interface. It would be amazing if Image Cache could allow users the ability to use this interface for selecting exactly what part of an image should be a thumbnail, for example. I'm sure that there would be many other use cases as well.
As I said before, I'm not expecting this to become a reality any time soon... just throwing the idea out there to see if it inspires coders better than myself to take a stab at it.
Comments
Comment #1
mpare commentedI had an idea, though greatly different from the original feature request, but with a similar end result.
Before I begin my description I would like to extened an offer to help develop this and similar feature requests. I am not an experienced drupal developer but know enough to at least approach the enhancements.
So my feature would be called "Focus." And actually this feature may be better implemented into say something like "Image Attach Field" but would benefit from function features that could be built into image cache. The only reason I suggest this to also be added to "Image Attach Field" is for UI reasons, but the actual feature I believe has a place in image cache. What my feature would do is provide a function or just a parameter for image cache that would allow the user to input a "focus area" for the image. So since imagecache images can be scaled and resized and cropped this would add a priority to a region of the original photo. So say that I have an image and the subject in the image is on the far right, but by image is a landscape. So in my template I have requested that my image be scaled and cropped so that it would fit in a 90 x 90 area. Well my subject may now be completely cropped out of the image. So if there were a way in the imagecache function to say focus = 'mr' this would tell image cache to deliver focus on the image to middle-right. You could base these focus fields off the traditional rule of thirds. So you would have tl, tm, tr, ml, mm, mr, bl, bm, br. Where, tl = top-right, tm = top-middle, tr = top-right, ml = middle-left, mm = dead center, mr = middle-right, bl = bottom-lect, bm = bottom-middle, and finally br = bottom-right.
So now I could render my image with focus to the far right. Now I think I could accomplish this without this being built into imagecache but if it were in image cache doing dynamic focus could be really easy. Because now I could be a ui for say cck image attach field. So you attach your image then you have a nother option and it has like a 3 x 3 table with a way to make a selection. So now I could click on the middle row right column box and have the information stored in the db. So now with image cache I could say ok, this image has focus information contained in it, so now imagecache will follow the rules and apply that focus. Now you could also build your theme function to ignore focus.
Wow, that's the first time I put that into writting so I don't know if that really makes that much sense, but I have a firm grasp on what I am wanting to do if anyone wants to talk about it. And again I would like to help develop this if there is some interest.
Thanks,
-mpare
www.paretech.com
Comment #2
mpare commentedI was just trying to add info to your original feature, I didn't mean to hi-jack your request. If there is a way to fix these two posts lets do that.
Sorry,
-mpare
www.paretech.com
Comment #3
rickvug commentedNo problem on the rename mpare, the interface isn't very clear. Changing to a more descriptive name.
Comment #4
quicksketchThis will never be a feature of imagecache. Imagecache is made to work off of presets. Anything suggesting image-by-image manipulation is not a part of the functionality. Fortunately, another module is being created just for this purpose :)
http://drupal.org/project/eyedrop
Comment #5
rickvug commentedQuicksketch - I understand your opinion and direction for imagecache and the need to keep it small and generalized. If eyedrop is the module to implement the feature that I am talking about then so be it. That said, do you see any collaboration between the two systems so that they complement eachother? For example, setup a rule that if eyedrop does not set the cropping for the image imagecache kicks in with the default? Let me know and maybe I'll switch this issue over to the eyedrop editor.
I love the module and think that it is well on its way to being one of the big "meta" modules that gets used all over the place.
Cheers,
Rick
Comment #6
dopry commentedrickvug, can you explain your use case? are you thinking that if an image hasn't been manipulated by eyedrop that it should be presented with imagecache... I think if you want that feature you're going to have to create it. Sime and I are working together. We're working on a common backend for file transformations that can be shared by eyedrop and imagecache. Your situation is one we haven't crossed yet... I'm suspecting it will be a custom handler....
.darrel.
Comment #7
dopry commentedrickvug, can you explain your use case? are you thinking that if an image hasn't been manipulated by eyedrop that it should be presented with imagecache... I think if you want that feature you're going to have to create it. Sime and I are working together. We're working on a common backend for file transformations that can be shared by eyedrop and imagecache. Your situation is one we haven't crossed yet... I'm suspecting it will be a custom field formatter.
.darrel.
Comment #8
rickvug commented"rickvug, can you explain your use case? are you thinking that if an image hasn't been manipulated by eyedrop that it should be presented with imagecache..."
Exactly. An easy example of this would be for an online store. For 90% of the image thumbnails Image Cache works perfectly. For others however, the crop isn't exactly right and needs to be tweaked. For these it would be great to go and edit the node and use eyedrop editor to make the thumbnail look exactly as you want.
As of right now I don't have the time alloted (nor the skill!) to make this happen. It would be handy however and I'm sure my use case is common so I'll move this over to the eyedrop editor queue where it'll likely sit for a long while.
Cheers,
Rick
Comment #9
simerickvug said:
Absolutely! :-)
rickvug, at the moment we haven't really started integrating two systems. My current version of Eyedrop is more or less self-contained for a current job and I'm now focussing on getting it stable (because it's not yet).
Transformer, Imagecache, Eye-drop want to rent a room together, but there's a long way to go. Contact me my email and I'll give you a logon to look at a demo for Eye-drop so far.
Comment #10
rickvug commentedChanging back to the Imagecache queue and closing. http://drupal.org/project/imagecrop and http://drupal.org/project/imagefield_crop both build off of Imagecache and implement the exact functionality described in this thread. Glad to see all of this coming together so well.