On Thu, 2010-03-25 at 16:28 +0000, Phil Endecott wrote:
Christian Henning wrote:
[snip]
Also, how would a C++ wrapper help you with large images?
My point is that your gil interface doesn't help me with large images in limited RAM, and your current design is "all or nothing". Decomposing it into wrappers around the libraries that are independently useful would mean that I could use them directly and get the benefit of e.g. the error handling stuff, with my own row-at-a-time code on top.
I second that. I'll probably need this library quite badly next month. So I could gladly help coding. Also, allowing a more low-level abstraction permits creating image types for images that do not live in memory. Which, IIUC, is what Phil really needs in his TIFF use-case.
Phil.
Regards, -- Felipe Magno de Almeida
