AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
June 2011

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems



Valid HTML 4.01!



Thread

2011.06.30 15:21 "Is it possible to read a large tiff image in portions?", by Hib Eris
2011.06.30 15:45 "Re: Is it possible to read a large tiff image in portions?", by Olivier Paquet
2011.06.30 15:48 "Re: Is it possible to read a large tiff image in portions?", by Bob Friesenhahn
2011.06.30 15:51 "Re: Is it possible to read a large tiff image in portions?", by Steve Mills
2011.06.30 15:52 "Re: Is it possible to read a large tiff image in portions?", by <jcupitt@gmail.com>
2011.06.30 16:02 "Re: Is it possible to read a large tiff image in portions?", by David Burken
2011.06.30 20:16 "Re: Is it possible to read a large tiff image in portions?", by Hib Eris
2011.06.30 20:35 "Re: Is it possible to read a large tiff image in portions?", by David Burken
2011.07.01 04:57 "Re: Is it possible to read a large tiff image in portions?", by Andreas Kleinert
2011.07.01 14:12 "Re: Is it possible to read a large tiff image in portions?", by David Burken

2011.07.01 14:12 "Re: Is it possible to read a large tiff image in portions?", by David Burken

On 07/01/2011 12:57 AM, Andreas Kleinert wrote:
>> That would be a good addition.  All the higher level libraries that link
>> with libtiff write their own(like ossim) so it would save a lot of
>> duplicate code.
> Well, actually, what is the problem with 3rd party libraries? Duplicate
> code isn't really a valid argument, as within such application you would
> only use one of that libraries. Duplicate code maintenance might be
> true, but that is the problem of their authors - and then again libtiff
> code maintenance is a topic on its own as well (and such new functions
> wouldn't flawlessly do their job on every possible sort of TIFF from the
> very beginning; the RGBA functions don't either - but the user
> expectation would be that everything is handled gracefully for any
> possible input... possibly huge support overhead)

So I woke up in the middle of the night thinking libtiffutils...

I agree I hate the thought of polluting libtiff.

Dave