-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[OUTDATED] Roadmap v3 #2
Comments
I've forked this though it's brutal - only useful for horizontal merge. |
@elipeters Isn't it good enough with Could you explain more about the |
All websites were once built this way... slice up a large image and place inside tables then http request the heck out of it. ...though now in reverse... output something like... imgDimensions:{
width: [img1.width(), img2.width(),...],
height: [img1.height(), img2.height(),...]
} or map:[
img1: {x,y,width,height},
img2: {x,y,width,height},...
] I apologise if I am not being clear. :) |
Okay, based on what you said, I believe this is basically a serialized output for the metadata of composed images. Please correct me again if it differs to what you thought. In fact, there are couple of api in v3 (but not in v2) that expose the calculation of image chunks to allow a custom plugin for a image composition. Maybe someone or me can write some plugin for this module to extract json-like object for the output via this api. |
I would like to help this one
But I am not sure what is the specific definition about these strategies |
Remove globaloffsets
in favor of individual offsets.mode
option so that user can choose either of merging strategiesmerge
,concat
,grid
,custom
(no default offsets according to image size, fixes Question about option #4).README.md
The text was updated successfully, but these errors were encountered: