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
December 2004

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

2004.12.08 02:35 "Q: writing tiled TIFFs", by Chris Losinger
2004.12.08 02:51 "Re: Q: writing tiled TIFFs", by Bob Friesenhahn
2004.12.08 02:55 "Re: Q: writing tiled TIFFs", by Chris Losinger
2004.12.08 02:57 "Re: Q: writing tiled TIFFs", by Bob Friesenhahn
2004.12.08 08:00 "Re: Q: writing tiled TIFFs", by Sachin Garg
2004.12.08 15:56 "Re: Q: writing tiled TIFFs", by Bob Friesenhahn
2004.12.09 07:28 "Re: Q: writing tiled TIFFs", by Sachin Garg
2004.12.08 10:01 "Re: Q: writing tiled TIFFs", by Sachin Garg
2004.12.08 12:41 "Re: Q: writing tiled TIFFs", by Chris Losinger
2004.12.08 12:48 "Re: Q: writing tiled TIFFs", by Joris Van Damme
2004.12.09 02:30 "Re: Q: writing tiled TIFFs", by Chris Losinger
2004.12.09 07:27 "Re: Q: writing tiled TIFFs", by Sachin Garg
2004.12.09 10:12 "Re: Q: writing tiled TIFFs", by Joris Van Damme
2004.12.09 12:48 "Re: Q: writing tiled TIFFs", by Chris Losinger
2004.12.09 13:19 "Re: Q: writing tiled TIFFs", by Joris Van Damme
2004.12.09 13:38 "Re: Q: writing tiled TIFFs", by Chris Losinger
2004.12.09 14:01 "Re: Q: writing tiled TIFFs", by Joris Van Damme
2004.12.09 23:09 "Re: Q: writing tiled TIFFs", by Chris Losinger
2004.12.09 23:29 "Re: Q: writing tiled TIFFs", by Bob Friesenhahn
2004.12.10 06:53 "Re: Q: writing tiled TIFFs", by Sachin Garg
2004.12.10 21:28 "Re: Q: writing tiled TIFFs", by Andrey Kiselev
2004.12.10 21:52 "Re: Q: writing tiled TIFFs", by Bob Friesenhahn
2004.12.10 21:55 "Re: Q: writing tiled TIFFs", by Andrey Kiselev
2004.12.10 21:54 "Re: Q: writing tiled TIFFs", by Chris Losinger
2004.12.10 21:47 "Re: Q: writing tiled TIFFs", by Andrey Kiselev
2004.12.10 21:56 "Re: Q: writing tiled TIFFs", by Bob Friesenhahn
2004.12.10 21:41 "Re: Q: writing tiled TIFFs", by Andrey Kiselev
2004.12.08 13:49 "Re: Q: writing tiled TIFFs", by Sachin Garg
2004.12.08 13:22 "Re: Q: writing tiled TIFFs", by Chris Losinger
2004.12.08 14:05 "Re: Q: writing tiled TIFFs", by Sachin Garg

2004.12.08 13:49 "Re: Q: writing tiled TIFFs", by Sachin Garg

> > > is there a simple tutorial for writing tiled TIFFs? i've looked at the
> > > sample apps, but i'm not quite sure what all is going on in there. you C
> > > guys sure do hate whitespace and passing parameters where a global variable
> > > will suffice!
> >
> > Rather than assuming whatz correct and whatz not, you must try to
> > understand that there can be more than one correct way of achieving
> > the same results. Just because you are not accustomed/familiar with a
> > style is a perfectly wrong reason to disregard something which works
> > perfectly (or atleast good enough)
> 
> hold on. i never said their code wasn't "correct".
>
> i'd just prefer to see a simple explanation of what TIFFWriteTile
> expects, what the rules are for tile sizes, what z-order means here, etc..

Technically your question is ofcourse valid and I am sure you would
have got your reply in the other more informative posts.

Its just that that your opinion, rather remark, on "the C guys" was
not needed and not 'correct' here either. I just have three things to
say:

1) It is possible to write very elegent C code. (Although I myself prefer C++)

2) I dont remember reading much badly-coded C-code in libtiff.

3) Such opinions, especially when you are requesting assitance, may
result in you not getting any informative replies. Fortunately for
you, the guys here are much more level-headed than most other
forums/mailing-lists/newsgroups I visit.

My apologies if i sounded a bit rude.

btw, Many open-source projects dont have documentation good-enough for
those who are new to the particular application domain (and thatz
perfectly ok). Code itself is the most comprehensive documentation
(although not always easy to read). Thatz why I suggested that book on
code-reading which taught me some things.

 Best of luck :-)


-- 
Sachin Garg [India]
http://www.geocities.com/schngrg