[
https://issues.apache.org/jira/browse/PDFBOX-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14311025#comment-14311025
]
Maruan Sahyoun commented on PDFBOX-2580:
----------------------------------------
We can put everything into the PD model - but should we? I don't think we
should.
Appearance generation, block formatting, rich text handling, default field
styles (and if we are to support annotations properly similar items for these)
don't have a direct reference in the PDF specification or are incorporated into
the spec. IMHO they don't belong to the PD model as to me PD also means that
this is (well) defined in the PDF specification.
By having that - especially the implementation specific parts of the appearance
generation which are not defined in the PDF specification - in a separate
package we differentiate the defined part from the undefined part because the
undefined part is our own interpretation of how that shall be done.
As an added benefit it will allow to better modularize PDFBox. E.g. one could
leave out the forms creation capability easily (but still has the ability to do
it himself by using the PD model).
Finally I do know about the Sonar issue. To me that's an intermediate issue as
this only happens as appearance generation is currently triggered in
.interactive.forms but handled by .services.forms. I had planned to remove that
anyway so appearance generation will only be done via .services.forms. and no
longer triggered from .interactive.forms. A lot of the Sonar issues AcroForms
originally had before I started working on that package are already resolved.
> 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]
