To make the upgrade to 4D 16 64-bit, I replaced 4D Write with a Markdown editor using a rich text area with some expression editing features. HTML generated from Markdown is converted to PDF using PhantomJS. Seems to work well and no complaints from users.
PhantomJS is losing future support, but both Google Chrome and Firefox support headless mode for generating PDFs. And there is all kinds of open source software for driving that on a server including some HTTP APIs. https://github.com/RelaxedJS/ReLaXed https://github.com/mozilla/geckodriver https://w3c.github.io/webdriver/ John DeSoi, Ph.D. > On Jun 14, 2018, at 10:22 AM, Kirk Brooks via 4D_Tech <[email protected]> > wrote: > > Making PDFs is hard. True - with a Mac or Win10 it's become pretty easy to > print-to-PDF. This is really a user-interface feature though. If you need > to build a PDF in code and want to work with the BLOB of that document > using the OS print features starts to fall apart. If you want to do this on > the server it's a complete non starter in my view. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
