My friends. Many years have passed and you have not implemented a single method for obtaining a processed image. Probably when the bundle was first created, you relied on the template engine and the URL addresses of the images in the templates. Today, most websites and applications operate on API principles. The existing functionality does not allow you to simply receive a processed image.
You have something like this createFilteredBinary function - in reality, you need a function that returns the imageBinary based on the parameters ($path, $filter) The point is to get a completely processed image given $config['default_image'] with saving to cache if it is not there exactly as it does createFilteredBinary function but return imageBinary
hi, your message comes across quite condescending. not everybody will have your use case. that said, we are currently in the process of rethinking the core interfaces of this library in 1590.
My friends. Many years have passed and you have not implemented a single method for obtaining a processed image. Probably when the bundle was first created, you relied on the template engine and the URL addresses of the images in the templates. Today, most websites and applications operate on API principles. The existing functionality does not allow you to simply receive a processed image.
You have something like this
createFilteredBinary
function - in reality, you need a function that returns the imageBinary based on the parameters ($path, $filter) The point is to get a completely processed image given $config['default_image'] with saving to cache if it is not there exactly as it doescreateFilteredBinary
function but return imageBinary