Skip to content
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

Overlay Processor #113

Closed
chrisdrackett opened this issue Mar 2, 2012 · 7 comments

Comments

@chrisdrackett
Copy link
Collaborator

@chrisdrackett chrisdrackett commented Mar 2, 2012

A processor that takes one image (potentially with an alpha channel) and overlays it on a second image to create a final image.

@matthewwithanm

This comment has been minimized.

Copy link
Owner

@matthewwithanm matthewwithanm commented Mar 2, 2012

Yeah, I almost added this! One thought: an "underlay" equivalent would also be nice. Not sure if it's a different processor or the same with different args.

@chrisdrackett

This comment has been minimized.

Copy link
Collaborator Author

@chrisdrackett chrisdrackett commented Mar 2, 2012

Maybe this would just be called "stack" and takes a top and bottom image. Maybe it even takes a list?

@dmishe

This comment has been minimized.

Copy link

@dmishe dmishe commented May 18, 2012

in the case of stack you should be able to specify original image index in that stack, so you can compose
background -> original -> overlay

@chrisdrackett

This comment has been minimized.

Copy link
Collaborator Author

@chrisdrackett chrisdrackett commented May 18, 2012

yeah, I think being able to stack as many images as you want is a good idea. I'm going to start this on a branch today and see how it goes

@matthewwithanm

This comment has been minimized.

Copy link
Owner

@matthewwithanm matthewwithanm commented Jun 30, 2012

I think indexes would overcomplicate the processor. You can always compose multiple instances to put some layers above and some below. I guess I'd have to see the API you had in mind to be sure though.

@dmishe

This comment has been minimized.

Copy link

@dmishe dmishe commented Jun 30, 2012

Actually i agree with you. I made overlay processor for out project and just chaining processors could work very well. And in case you need something more complicated you just subclass/make your own

On 30 черв. 2012, at 16:44, Matthew Tretter reply@reply.github.com wrote:

I think indexes would overcomplicate the processor. You can always compose multiple instances to put some layers above and some below. I guess I'd have to see the API you had in mind to be sure though.


Reply to this email directly or view it on GitHub:
#113 (comment)

@matthewwithanm

This comment has been minimized.

Copy link
Owner

@matthewwithanm matthewwithanm commented Aug 19, 2013

Now that PILKit has been split off, this probably doesn't belong in django-imagekit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.