[
https://issues.apache.org/jira/browse/PDFBOX-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328501#comment-16328501
]
Maruan Sahyoun commented on PDFBOX-4068:
----------------------------------------
Sorry if I it was unclear - yes, I think it would be good to keep
{{PDAppearanceContentStream}}.
For various reasons I couldn't continue to work on it but have some spare time
now. If you are fine with it I'd like to
# keep PDAbstractContentStream containing the basics operations wo state
handling
# decorate that in PDAppearanceContentStream with state handling and higher
level operations
# if that proves to be usable do the same in PDPageContentStream (or if
preferred move it back to the old state before PDAbstractContent was introduced)
> 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: [email protected]
For additional commands, e-mail: [email protected]
