[ 
https://issues.apache.org/jira/browse/PDFBOX-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350892#comment-16350892
 ] 

Tilman Hausherr commented on PDFBOX-4068:
-----------------------------------------

Yes for 1 and 4... about 2: why? I'd expect this to be identical. 3: it is used 
for much more... see the implementation of the highlight and line handlers: 
xobject forms and extended graphics states and fonts. Using 
{{PDAbstractContentStream}} as a member does not sound good at all, how would 
we have mostly identical methods for each class?

> Create ContentStream for XObject forms
> --------------------------------------
>
>                 Key: PDFBOX-4068
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-4068
>             Project: PDFBox
>          Issue Type: Task
>          Components: PDModel
>            Reporter: Tilman Hausherr
>            Priority: Major
>
> We have a {{PDAppearanceContentStream}} for appearances but nothing for 
> XObject forms.
> What we need should extend {{PDAbstractContentStream}} and should have a 
> constructor like
> {code:java}
> public PDFormContentStream(PDFormXObject form) throws IOException
> {code}
> Alternatively, why not replace {{PDAppearanceContentStream}} ? Its parameter 
> {{PDAppearanceStream}} is extended from {{PDFormXObject}} so we could just 
> use the base class.
> We need this both for 2.0 and 3.* - we have users who have a really hard time 
> fiddling with low level operators instead of using the methods.
> In 2.0 we could replace the parameter of {{PDPageContentStream}} that is 
> currently {{PDAppearanceStream}}. This would be a non breaking change.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org

Reply via email to