The iText 5 class names
PdfPCell were chosen because we already had classes named
Cell to create table and cell objects at the highest programming level. There was also a class named
PdfTable to be used by iText internally. Those classes had a lot of flaws and they were deprecated in favor of
PdfPCell. They have been removed a long time ago.
Over the years,
PdfPCell also received some criticism from users. For instance: users didn't understand the difference between text mode and composite mode.
Text mode is used when you create a
PdfPCell like this:
cell = new PdfPCell(new Phrase("Cell with rowspan 2"));
In this case, you define properties like the horizontal alignment on the level of the
Composite mode kicks in the moment you use the
cell = new PdfPCell(); cell.addElement(new Phrase("Cell 1.2"));
In this case, some properties defined at the level of the
PdfPCell (such as the horizontal alignment) are ignored. The horizontal alignment is to be defined at the level of the elements added to the cell. For instance: if you want to create a cell in which different paragraphs need to have a different horizontal alignment, you will switch to composite mode.
If you look at the screen shot of the table created with the iText 5 example, you will notice that the cells with content Cell 1.1 (added in text mode) and Cell 1.2 (added in composite mode) are aligned quite differently.
In answer to the criticism on the odd alignment, we introduced methods to use ascender and descender information. We use these methods for the cells with content Cell 2.1 (added in text mode) and Cell 2.2 (added in composite mode). We also introduced a padding of 5 for these cells.
Now the result is much better.
What we fixed in iText 7:
Since we created iText 7 from scratch, we had no legacy classes with names we couldn't reuse. We introduced a new
Table and a new
There is no more text mode and no more composite mode. A
Cell is created either without parameters, or with parameters that define the rowspan and the colspan. All content is added the same way: using the
Our customers were also asking to provide a means to distinguish a margin and a padding. In the iText 7 example, we added a gray background to show the difference. In the cell with content Cell 2.1, we define a margin of 5 user units. The default padding is 2. In the cell with content Cell 2.2, we define a padding of 5 user units, the default margin in 0.
As you can tell from the screen shots, the cells are rendered quite nicely. We didn't have to use methods to set the ascender or descender. The default behavior is much closer to the behavior a developer would expect.
Want to know more about tables and cells in iText 7?