Feature Request: Easy way to make the package work with intervention cache

[rawzone]

Trying out this package and quite like so far!

However we almost always uses Intervention cache package with the Intervention image package to have easy access to multiple image sizes via the url caching / templating.

Would be wonderful if this package had an easy way to make use of the caching package.

I guess it would be able to be installed manually and just using the database column data to seup the custom URLs for the images in need. But would be nice if methods like $model->imageTag() had the support.

Thanks.

[rawzone]

This could also allow for the use of responsive images.

If there is multiple size of the same image there could be a $model->responsiveImageTag() that could return an image tag with srcset etc.

[saqueib]

sound good to me, I will do it soon

[saqueib]

@rawzone please share some sample code on how you currently use this cache package with intervention image so I can work on integrating it. In docs I find only this:

// pass calls to image cache
$img = Image::cache(function($image) {
    $image->make('public/foo.jpg')->resize(300, 200)->greyscale();
});

[rawzone]

@saqueib sure. It's not really just a piece of code - The documentation desribes it pretty well.

But you setup filters for handling images (Anything from resize/blur/black&White etc).

You tell the package which folders / paths to look for image names / folders - This will be used in the final URL for the image.

Then setup a route (The package does this via its config file) for handling the cached version of the images and refere that URL in your blade templates.

When requested by a client this will create a cached version of the image defined by the filter and any other request within the TTL will be served the cached version no requiring the server to handle the image conversion again.

Hope that makes sense.
If you have any questions please let me know.