[ https://issues.apache.org/jira/browse/PDFBOX-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336804#comment-14336804 ]
Maruan Sahyoun commented on PDFBOX-2692: ---------------------------------------- IMHO there has to be a line between public and private but that line has to be adjusted based on users feedback. Both use cases outlined here look fine for me and should be supported. Daniels use case: I wouldn't know a different way to support Daniels uses case other than allowing him to override PageDrawer but I'm not a specialist in this area. Manfreds use case: For Manfreds use case I'm not sure - looks like that could (and maybe should) be handled differently as Annotations are extendable per PDF spec (which we don't allow at that point in time). So it might be better to 'register' new/custom annotations with annotation handlers being responsible for presentation and other sorts. But I would need to understand the use case and the limitations better. What we should avoid is leaving people behind so I'm very happy that Daniel and Manfred speak up and discuss what they believe is a limitation. > Possibility to use our own and/or overwrite PageDrawer class > ------------------------------------------------------------ > > Key: PDFBOX-2692 > URL: https://issues.apache.org/jira/browse/PDFBOX-2692 > Project: PDFBox > Issue Type: Wish > Components: Rendering > Affects Versions: 2.0.0 > Environment: JDK 1.8, Windows 7, PDF-Box - current trunk > Reporter: Manfred Pock > Labels: features > > We use PDFBox to render PDF's. Additionally, we have the posibility to add > different kinds of annotation (stamp, marks, free text, notes..) like in a > wysiwyg-editor. To do this, it is necessary that we paint these annotations > on our own. > Another reason is not to paint all parts: for example we have a pdf with an > embedded picture. Behind the picture we have the OCR-text to this picture. > This text is only needed for searching und should not be painted. > Thus it would be useful to use our own derived PageDrawer. As I see there are > some things to change. > a.) remove the final from PagerDrawer-class. > b.) make some global-variables (graphics, xform, pageSize...) protected, > c.) also some methods like setRenderingHints should be protected > d.) maybe the possibility to say to the PDFRender which PageDrawer should be > used. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org