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

Remove ImageMagick, use FreeImage instead #413

Merged
merged 1 commit into from
Jun 7, 2018

Conversation

tribal-tec
Copy link
Contributor

No description provided.

@tribal-tec tribal-tec force-pushed the master branch 2 times, most recently from 6a684d6 to 5e603ef Compare June 7, 2018 08:31
@tribal-tec tribal-tec requested review from favreau and rdumusc June 7, 2018 08:31
Copy link

@rdumusc rdumusc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

BYTE* pixels = NULL;
DWORD numPixels = 0;
FreeImage_AcquireMemory(memory.get(), &pixels, &numPixels);
return {base64_encode(pixels, numPixels)};
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't this whole block go as a function into ImageUtils?

return true;
}

ImagePtr getImageFromFrameBuffer(FrameBuffer& frameBuffer)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

getImageFromFrameBuffer and SwapRedBlue32 should go into ImageUtils.cpp. You can get compilation errors about double definitions if you try using them in two places, unless the function are inlined, but I don't see a good reason to inline them.

@tribal-tec tribal-tec merged commit a78b983 into BlueBrain:master Jun 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants