Closed (won't fix)
Project:
ImageCache Actions
Version:
7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
6 Apr 2010 at 23:04 UTC
Updated:
20 Mar 2016 at 14:25 UTC
Jump to comment: Most recent
Comments
Comment #1
dman commentedOuch.
I can see where you are going with this (pretty clear description) but what a headache!
- It'll need to support both scale and scale+crop
- the radiuses you mention are probably overkill, if it can be done with maths instead
- What I can't figure is how to deal with snapping of both width and height, or cases where one but not another dimension is given. Really flaky heuristics.
In the actual case, you probably just want to switch between two (maybe three) presets, so probably be best to use customactions, some code specific to your actual task, and pass off to a chosen preset the way that the aspect switcher does. :-/
Comment #2
yellek commentedYou can see the problem I am trying to solve on http://www.hopevalleyuc.org.au/content/women-hope. On that page the image is floated left and set not to scale up. I want to guarantee a minimum width for the text whilst still having it wrap around the image if the image is small enough. The simple version of the feature would do this.
Width and height won't be too bad if you calculate the "distance" from an ideal size by adding the absolute values of the x and y differences in size. Also I'm probably more interested in scaling than cropping as if you can crop the image the situation I am trying to solve becomes less of a problem.
Comment #3
yellek commentedI've had a bit of a think about how the algorithm would work and, as I'm not a PHP developer, I present it here in pseudo code.
I'm not so hot on the UI side so a UI to capture the bounding boxes as well as the inside and outside snap would have to be devised.
Does this algorithm seem feasible?
Comment #4
fietserwinAssigning a version. If we implement it, it will be in 7.x-1.x.
Comment #5
fietserwinI guess this is:
- To specific
- To much detail to specify (cluttered UI)
- Relatively easy done with a custom action that fills the data for a resize/scale effect and calls that effect.
So tagging as won't fix.