You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "John Hewson (JIRA)" <ji...@apache.org> on 2014/03/05 21:20:43 UTC

[jira] [Created] (PDFBOX-1962) Refactor the packages in the core pdfbox module

John Hewson created PDFBOX-1962:
-----------------------------------

             Summary: Refactor the packages in the core pdfbox module
                 Key: PDFBOX-1962
                 URL: https://issues.apache.org/jira/browse/PDFBOX-1962
             Project: PDFBox
          Issue Type: Improvement
    Affects Versions: 2.0.0
            Reporter: John Hewson


We want to refactor the core pdfbox module packages so that there is no longer a dependency on AWT. Any packages which are moved outside the of the org.apache.pdfbox module need to be re-packaged appropriately (e.g. org.apache.pdfbox.rendering).

AWT code could live in "pdfbox-rendering" but we need to think carefully about how to do this because, e.g. some of the Filters use AWT, as does FontBox.

What are the use cases for modularisation, currently we have:
- Android
- Google App Engine

Android seems to have some support for AWT and ImageIO, can somebody in the know provide more information?

Google App Engine seems to blacklist ImageIO and AWT classes. Is there a strong desire to support it?



--
This message was sent by Atlassian JIRA
(v6.2#6252)