Added PasteFilterLoader

[lmcd]

Added a filter loader for the 'Paste' filter. I really think there ought to be loaders for all the in-built Imagine filters so everything works out the box.

Example configuration for adding a watermark to an image:

liip_imagine:
    filter_sets:
        product_image:
            quality: 90
            filters:
                paste: { start: [577, 375], image: web/img/watermark.png }

P.S. bundle is a life-saver! Thx!

[avalanche123]

You can jut call $image->paste(), without using an extra filter object

[avalanche123]

Actually, looks like you misunderstood the interface. You need to prepare a filter in filter loader, not apply it, but just return it. In your case, you should open image that is specified in the options and return paste filter instance passing that image and point in constructor

[avalanche123]

Looks like you are submitting something for a different imagine bundle, configuration is not what this bundle expects

[lmcd]

Whoops, looks like this code was intended for LiipImagineBundle which does return the image. Are there any real benefits to using LiipImagineBundle over AvalancheImagineBundle?

[avalanche123]

I don't understand your question, you clearly picked LiipImagineBundle for some reason :)

[lmcd]

Was searching knpbundles for something to scale images on the fly (without prior knowledge of Imagine). Stumbled on LiipImagineBundle, read through the documentation and examples and it seemed to fit my requirements perfectly.

Comparing the two, they seem largely similar (LiipImagineBundle being a fork and all). LiipImagineBundle claims extensibility as the reason for it's existence but I'm curious how exactly it differs. Also wondering if FilterLoaders are incompatible by design.

[avalanche123]

My subjective summary would be that AvalancheImagineBundle is the minimalistic core to build on top of

[lmcd]

Ah, I found the refactoring debate here: #25
It's a shame FilterLoaders are incompatible between the two, or I'd create a whole set of them :(