Description
The way in which PDFBox handles the Page tree needs to be rewritten, preferably from scratch. Currently the document catalog returns the raw objects from the page tree, wrapped in either a PDPage or PDPageNode.
We need to abstract over the page tree and get rid of PDPageNode, we should provide methods which can add/remove PDPage objects only. The existing low-level access to the page tree is not needed at the PD-level.
Inheritance of page properties such as crop box, resources, and rotation should be reimplemented to use whatever new page tree abstraction we invent. We can finally remove the old broken methods which didn't look up the inheritance tree when retrieving these values.
Attachments
Attachments
Issue Links
- blocks
-
PDFBOX-2400 Add insertPage() method
- Closed
- breaks
-
PDFBOX-2792 Text extraction ignores bookmarks
- Closed
-
PDFBOX-3362 PageLayout.TwoColumnRight was Illegal
- Closed
- incorporates
-
PDFBOX-2708 PDDocument.removePage() deletes the last page regardless of parameter passed
- Closed
- is related to
-
PDFBOX-2494 NumberFormatException
- Closed
-
PDFBOX-2704 PDPageTree.indexOf doesn't find page numbers
- Closed
- is superceded by
-
PDFBOX-3000 Transparency Group issues
- Closed
- supercedes
-
PDFBOX-1903 refactor pdmodel (pdpage)
- Closed
1.
|
Create a PDTransparencyGroup for added code clarity | Closed | Unassigned | |
2.
|
Rename PDGroup to PDTransparencyGroupAttributes | Closed | Unassigned |