Hmm, howardgrigg, I think you are right, this is also a very important thing. Right now I'm not dealing with that problem, but I guess this might become a problem for me, too, soon.
So UncleCheese... Next round :D
This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.
Please use forum.silverstripe.org for any new questions
(announcement).
The forum archive will stick around, but will be read only.
You can also use our Slack channel
or StackOverflow to ask for help.
Check out our community overview for more options to contribute.
Hmm, howardgrigg, I think you are right, this is also a very important thing. Right now I'm not dealing with that problem, but I guess this might become a problem for me, too, soon.
So UncleCheese... Next round :D
I wish such a thing were in my hands, but unfortunately, all of that is handled by the Silverstripe GD class and the solution would lie in extending that class with custom modifications.
Hmm, so I guess I would have to modify writeTo($filename) in the GD extended Class ?
And I would have to copy paste all the original Image methods that use the normal GD class to my extended Image Class and rewrite them, so that they use my extended GD Class ?
Or do you know an easiyer way / an exact point/method that would do the trick ?
If this is beyond your knowledge, I would open another thread, but maybe theres something I would have to add/modifiy to the DataObjectManager, too ?!