CROPIT IMAGE DRIVER

cropit is called, so you can hide the slider and the file input in CSS. I do plan to add a cropit-destroyed class to the element where.

Laravel supports popular caching backends like Memcached, Redis, DynamoDB, and relational databases out of the box.

CROPIT IMAGE DRIVER

In this file, you may specify which cache driver you would like to be used by default throughout your application. Should this happen as part of the destroy method? My thought is that destroy should disable the slider since it's already taking care of it in many cases, but it should not hide/remove the slider and the file input since they were there before. Your applications cache configuration file is located at config/cache.php.

I suppose you would like to disable/hide the slider and the file input when cropit is destroyed.

Should it keep the background image outside the preview area (if available)? My hunch is no, since the element was added by cropit when initialized, and it's not very useful when cropping is disabled.

Cropbox is a lightweight jQuery image cropping plugin that creates a viewport around a given image allowing to move, zoom, resize and crop an image. It works on desktop and mobile with touch support. It loads images locally via FileReader, and crops them using canvas.

Should it leave the cropped image in the preview area? I suppose yes. CropIt is a jQuery plugin for image cropping and zooming.

However I do wish to understand more about the desired behavior of destroy: One thing I can definitely do is to improve the destroy method and make it unbind all the listeners on the preview area, the slider, and the file input. The technology for 'Freeform Cropping' on the iOS devices is PATENTED and is used in this APP. you are correct that the current destroy method doesn't actually unbind the listeners and I felt like it's not yet usable enough which is why I have not documented it. CropIt has been designed from the ground up to enhance the productivity of professionals on the go This ALL-IN-ONE solution is the ultimate tool in the app store - Large size Documents or Images may take some time to open / edit / save / send etc. Thanks for bringing up this interesting use case.

Cropit image