>>12
While looking for causes behind the last thirty odd hours of absolute shit on /prog/ it came to my attention that /b/ was down. In the meantime I propose we suggest they go Back to /g/, please.
>>13
Perhaps we should direct them to /lounge/ instead.
Name:
Anonymous2009-05-07 23:02
why the fuck would you do image handling in C/C++?
Even though I'm sure there's some kinda of archaic library out there that would help, i don't know google it fuck. Anyways,
You can write do it in about two or three lines using MSVC. If you want something more platform agnostic- your SLOC could easily get into the hundreds.
>>15 why the fuck would you do image handling in C/C++?
What? It would be hell to parse/manipulate images in any other language. But since the question is only ``how do I call the C/C++ function that already does the image handling'', it doesn't matter what language you use.
>>19 Image Processing Expert Relying on obscure open source forge hosted libraries to handle image proceessing and drawing- perhaps the single most important thing for usability in any application IHBT
>>25
I am very pleased to say announced you have been `Meta`-trolled. How does that feel, to have been `meta`-trolled by a master troll? Here's a nickel kid, go tell somebody who cares.
>>21
I don't actually use CImg in my programs. I do my critical, speed-limiting processing with a few custom functions, along with high-quality libraries such as FFTW for the ÜBER-OPTIMIZED stuff, and I use Qt and raw OpenGL for the GUI/display. I have also used VTK and ITK for the crazier stuff like segmentation and volumetric rendering of medical data.
CImg is slow as fuck and limited, but it's easy to use and a very quick way to get a DQN PROGRAMMER to display his shitty image. A bit like you'd use Matlab to check out some data and validate your algorithm before spending 9001 hours on a C++ implementation.