[
https://issues.apache.org/jira/browse/PDFBOX-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317732#comment-14317732
]
Maruan Sahyoun commented on PDFBOX-2580:
----------------------------------------
{quote}
Perhaps we should open a new JIRA issue which specifies this clearly?
{quote}
There is PDFBOX-2333 to track that - at least for PDFBox 2.0.
{quote}
their own "mutipdf" package
{quote}
maybe all of these can have a common package where e.g. multipdf, rendering,
printing would be a child to.
{quote}
rendering and printing out into their own module
{quote}
if we can remove AWT within PD and fontbox without doing a major release we
could do so right now otherwise I'd do that move in the major release having
the AWT removed (if that will every be done).
{quote}
AWT an that is the real problem and is much more complex and difficult to solve
{quote}
I trust that you'd be able to handle that. If that's something worth the effort
that's a different story. The current demand is to enable a full Android port
(some bits are already running there done by others).
> Decouple implementation specific forms handling from interactive.form PD Model
> ------------------------------------------------------------------------------
>
> Key: PDFBOX-2580
> URL: https://issues.apache.org/jira/browse/PDFBOX-2580
> Project: PDFBox
> Issue Type: Improvement
> Components: AcroForm
> Reporter: Maruan Sahyoun
> Assignee: Maruan Sahyoun
> Fix For: 2.0.0
>
> Attachments: sonar.png
>
>
> The interactive.form PD model currently holds classes reflecting the various
> fields intermixed with appearance generation and layout handling.
> In order to separate the PD model from the service of forms filling and
> appearance generation this functionality shall be moved into a new package.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
