[
https://issues.apache.org/jira/browse/PDFBOX-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14320840#comment-14320840
]
John Hewson commented on PDFBOX-2580:
-------------------------------------
{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}
Unfortunately it's a huge task with requiring some fairly deep API changes
(core often exposes AWT classes publicly in its own API).
{quote}
The current demand is to enable a full Android port (some bits are already
running there done by others).
{quote}
Yep, if that's the goal then it would provably be easier and less chaotic to
simply write a minimal AWT implementation for Android where we provide only the
classes and methods actually called by PDFBox and do that by wrapping the
Android graphics API.
> 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]
