There are still some issues when using Graphic Magick, as the "--gravity None" value is not allowed with Graphic Magick.
| Comment | File | Size | Author |
|---|
Issue fork image_effects-2991201
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
b-prod commentedComment #3
mondrakeThank you.
We need to allow tests for SetCanvas, Background and Mask to run with GraphicsMagick too, and see if they pass locally and/or in TravisCI - DrpalCI cannot run these tests atm.
Comment #4
b-prod commentedWhat am I supposed to do? Just remove the unset($toolkits['ImageMagick-graphicsmagick']); line on the test class for settCanvas?
Comment #5
mondrakeYes, that’s the way to allow tests to run on GM. Actually it’s probably sufficient to remove the entire method that overrides the base providerToolkits.
Comment #6
mondrakeDone #4/#5. Test results on TravisCI https://travis-ci.org/mondrake/image_effects/builds/429017955 :
Comment #7
mondrakeComment #8
mondrakeComment #9
mondrakeSome progress - this is no longer raising deprecations of ImageMagick methods and no errors at image style editing, but still fails the actual effects, https://travis-ci.org/mondrake/image_effects/builds/429071655
Comment #10
Christopher Riley commentedThis seems to have fixed my issue. I am going to do additional testing but thank you.
Comment #11
anskelt commentedThis stopped working with 8.x-3.4.
Comment #12
codebymikey commentedLooking into this
Comment #14
codebymikey commentedProvided a MR implementing the various effects for GraphicsMagick.
When it's not possible to apply certain effects in a single pass, a temp image is created (that'll be deleted at the end of the page request), and used for the desired effect.
And in the event that the effect is just a bit difficult to implement in GM, then it'll fallback to saving the current effects so far into a temporary image, then use that as the source for subsequent effects.
Whilst implementing this, I ran into the #3559034: [gm] Ensure ArgumentMode::PostSource applies after the source issue where arguments were always placed before the source image rather than after (breaking the desired effects).
I think a patch from that issue might be required in order to have the best experience with the effects.
Comment #15
codebymikey commentedAdded compatibility, and tests are passing.
Comment #16
codebymikey commentedComment #17
mondrakeNeed to watch #3552110: Remove manual create() method from plugins for avoiding service injection dances.
Comment #18
mondrake