Closed (won't fix)
Project:
ImageMagick
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
18 Aug 2014 at 19:30 UTC
Updated:
14 Sep 2015 at 09:09 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
mondrakeComment #2
sunLooks like that sandbox is a clean porting effort based on this project's actual repo — would you like to get commit access for the 8.x-1.x branch?
Comment #3
mondrakeHere's a patch against the current 7.x-1.x branch that would generate a possible 8.x-1.x branch. It's based on the work in the sandbox mentioned in the IS. There is review and more testing to do but locally this is working pretty much ok. I do not expect major changes to the image system API at this point of core development, so I thought it can be time to post here the current status of the sandbox.
A few points from the sandbox work:
Re. #2 I am fine to get commit access but can not promise to be able to maintain it ongoing, thanks.
Comment #4
mondrakeCouple of additions to #3:
Comment #5
berdirNice work, this seems to be working well.
The plugin isn't picked up after a module install, because the plugin managers aren't following the plugin.manager naming pattern, so the plugin_manager_cache_clear tag would need to be added those. Happy to review a core issue if you want to work on that.
Comment #6
mondrakeThanks @Berdir, not really sure I grasp what you mean. I confirm I am also seeing the toolkit only after refreshing all caches after a module install. Is it a problem with the core image toolkits plugin manager? If so, would you mind creating a core issue for that - I would need more details before I can say if I can work on that.
Comment #7
mondrakeNever mind, I think I understood. Created #2467775: Contrib toolkits are not picked up after module install in Drupal core issue queue.
Comment #8
aspilicious commentedJust some info. A closely related project http://www.drupal.org/project/imagick has also working code and a downloadable release.
Maybe it is a good idea to create a dev release as well for this module.
Comment #9
mondrakeRefreshed patch to take care of a few things that changed in core since #4 in Dec 2014 (immutable configuration, String class dropped).
Can anybody review core's #2311679: Separate MIME type mapping from ExtensionMimeTypeGuesser?
That would help to get rid of the workaround to get the image mimetype from the source format through a dummy filename
Comment #10
mondrakeAligned to current sandbox:
#8: +1
Comment #11
andypostHere's a big difference in modules - in-process and proc_open()
So maybe for 8.x better to merge them into one configurable module?
Comment #12
mondrakeUpdated after core's #1364670: ImageStyle::transformDimensions unable to deal with all effects., now AutoOrientImageEffect::transformDimensions() can use the original image EXIF data to determine styled image dimensions.
Can a maintainer open a 8.x-1.x dev branch?
Comment #13
mondrakeI got co-maintainership of this module and made a first commit, however different from the patch in #12. Will create a new plan issue to move forward.