I've been talking with Fuzzy76, and we've decided that the PDF-filling logic behind Certify and Fill PDF has a lot in common. We could abstract out the common parts so the individual modules could focus more on their actual applications and less on duplicating code. Additionally, Certify users would gain the ability to use Fill PDF Service as a fill method (opening it up to people on shared hosting, for example). And it would also let people contribute to one PDF-filling module and confer the benefits to users of all modules based on that one.

It makes a lot of sense.

The Certify version of this issue is: #1593928: Support other PDF generation methods

Comments

wizonesolutions’s picture

wizonesolutions
he/him
Primary language English
Location Norway
commented
Title: Abstract out PDF-filling logic into own module » Use PDF Forms API for PDF handling
Version: 7.x-1.x-dev » 7.x-2.x-dev

PDF Forms API has been born. Once it has an alpha release, Fill PDF should be converted to use that. A hard dependency on PDF Forms API will be added.

There won't be any work on an upgrade path yet - not until 7.x-2.x is ready for an alpha or beta release.

wizonesolutions’s picture

wizonesolutions
he/him
Primary language English
Location Norway
commented
Status: Active » Fixed

Whoa, this is actually basically done! PDF Forms API in itself still needs a lot more work, but, strictly speaking, Fill PDF 7.x-2.x-dev is now using PDF Forms API.

Anything arising from or related to this can be handed in separate issues now.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

(not verified) commented
Issue summary: View changes

Updated issue summary.