Jonas Wagner

Oh, sorry for missing this for so long. > Why do you always work with gamma encoded data? Is the performance difference that big? As far as I remember and...

Smartcrop always works with image data as input. You could feed it a 'blank' image and supply the faces in the boost parameter (as it's done in [smartcrop-cli](https://github.com/jwagner/smartcrop-cli/blob/master/smartcrop-cli.js#L101)). But at...

just take x/width*100 to get %.

> Based on your input image size, and desired crop area, the resulting relative crop area is (width) and (height) at coordinates (x) and (y). You must crop your image...

It's definitely worth considering. I haven't spent too much time thinking about it. I guess the main challenge is trying to balance it with other constraints. Another possible issue is...

I'm not aware of any port to iOS. The code is simple enough to port in a few hours though if you feel inclined to do so.

> Is there something I am doing wrong or some way around this? No, this sounds roughly right. The reason for this is in short, that I haven't used smartcrop...

At very least the summed area tables, yes. I'm surprised I didn't use them to begin with. They are such a simple, elegant and obvious solution. And I even had...

I now remember why I didn't use summed area tables for the integration step. It's because of the weighting function. So I guess this needs another trick to be made...

I investigated this a bit more and tried out both prescaling to a fixed size and the summed area tables approach in [this branch](https://github.com/jwagner/smartcrop.js/tree/integral-image). The prescaling seems to work nicely,...