[
https://issues.apache.org/jira/browse/PDFBOX-4853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120752#comment-17120752
]
Tilman Hausherr commented on PDFBOX-4853:
-----------------------------------------
No... also, most of these changes apply to both 2.* and 3.*. The main change I
can think of is that the trunk has an on-demand parser. Also, loading of
existing files is different ("Loader.loadPDF" vs "PDDocument.load").
> PDPageContentStream doesn't extend PDAbstractContentStream
> ----------------------------------------------------------
>
> Key: PDFBOX-4853
> URL: https://issues.apache.org/jira/browse/PDFBOX-4853
> Project: PDFBox
> Issue Type: Improvement
> Reporter: maltaisn
> Priority: Minor
> Fix For: 3.0.0 PDFBox
>
>
> Hi,
>
> I'm not sure if this is the right place to post this. I tried the FAQ mailing
> list 2 weeks ago and didn't get any response so I'll try here.
>
> I'm creating a PDF with transparency groups so I need to use
> PDFormContentStream, but also PDPageContentStream when not drawing to a
> transparency group. Transparency groups can be arbitrarily nested so I keep a
> stack of the current content stream to know which one to write to.
>
> However, what prevents me to keep the stack is that PDPageContentStream and
> PDFormContentStream have no common interface despite sharing nearly all the
> same methods. Is there any reason for this? I see there's already
> PDAbstractContentStream that's being implemented by PDFormContentStream,
> PDAppearanceContentStream PDPatternContentStream, but not by
> PDPageContentStream... Why?
> Currently this forces me to do [something like
> that|https://pastebin.com/p2FJw6GN] (Kotlin code) to artificially create an
> interface for both. It's pretty ugly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
