Matt Benson writes: > At the suggestion of David Freels, I am going to start > coding this myself. One interesting question: Why > does Graphic live in the com.lowagie.text package yet > inherit from com.lowagie.text.pdf.PdfContentByte?
Well, Paulo and I combine two completely different approaches. 3 years ago I wrote the original library called rugPdf. This library could only be used by people who knew a great deal about PDF. I received lots of PDF-related questions from people who just didn't understand the mechanisms behind PDF. So I completely redesigned rugPdf, I called it iText and I hid all the PDF functionality, allowing the user only to work with high level objects. Graphic was such a high level object. It inherited from the (now removed) class PdfContent. Then Paulo came along and little by little he added low level PDF functionality and made it available to the user (but in a far more userfriendly way than was the case with rugPdf). Class PdfContent was changed in PdfContentByte and class Graphic was updated for backward compatibility reasons. If you are only generating PDF straight from a application, you shouldn't use those high level objects such as Table, Graphic, HeaderFooter,... The reason these objects still exist, is because they allow you to create documents with content while making abstraction of the presentation format. This is exactly what we need when we convert XML to another format. > By the way, the original message is several months > old... I know, I know, it hurts to be remembered of all the plans I didn't realize... _______________________________________________ iText-questions mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/itext-questions
