[
https://issues.apache.org/jira/browse/PDFBOX-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14311260#comment-14311260
]
Maruan Sahyoun commented on PDFBOX-2580:
----------------------------------------
I fully understand your position and as I wrote before all of the forms
functionality can be implemented in the PD model. Not doing it there but in an
extra package has been considered knowing our PD model and knowing that
currently most of our stuff is in there. But as we add to PD we are moving away
- or at least make it more difficult - to modularize PDFBox which is one of our
longer term goals.
Maybe we can concentrate on one question first as this will simplify the
discussion a lot and from that decision everything can be worked on. Shall
there be a new package to start layering PDFBox further to foster
modularization (o.a.p.service in my approach) ?
> 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]
