TCPDF VS chai

Generating PDF documents out of your app's HTML output is a very common requirement and there are several open source libraries to accomplish this. I came across this need for my project recently and I evaluated many popular ones such as TCPDF, mpdf, FPDF, etc. But the one that truly stood up to my evaluation in terms of efficiency (minimal footprint) and ease of implementation was DOMPDF.

Leveraging Laravel for PDF generation involves utilizing its built-in features or integrating third-party packages. The framework supports popular packages like dompdf and TCPDF, making it easy to implement PDF generation with minimal effort.

TCPDF has full support for rendering an EPS into a PDF.

It can be fussy.

https://tcpdf.org/

Idk what’s the big problem. Maybe it’s just something like https://tcpdf.org ? Using that for years.

Depending on if this is a web-based project or not this suggestion might not be suitable. But the last few projects like this I did that were web-based I have used Google Charts with TCPDF. I rendered the charts on the page as a "print preview", and since TCPDF supports basic HTML composition I saved out the charts as generated images and submitted them to the server which generates a PDF. Bit convoluted but that was what I came up with in a hurry.

Running a headless browser to render HTML is a resource intensive task. If you only need to generate simple documents, you're better off using a tool that generates PDF directly. In the old days we used FPDF and its successors (TCPDF was the most popular). Both seem to have recent releases. There's also mPDF , that seems to be another child of FPDF.

You may want to look at a PDF library (Python/PHP/Perl/Java, etc.) You can do all you mention with a lot of flexibility. tcPDF comes immediately to mind, there is also a Python port. If you want to learn a language, i recommend python. Learning how to make a basic program when it is something that you want, and you know what you want is a great way to learn.

I would also look at dompdf and tcPDF, they would have very advantages if you intend to revise/reprint your documentation.

The original site still has it available for download, but most importantly, a ton of examples and documentation, that while I haven't tried the github version, probably works based on the same as the old.

But not just off-topic: abusive, and dishonest.

I'm not sure this even applies as we call the mutool binary installed via apt, rather than use or modify their libraries.

Even if it applies, Mu's AGPL requires you release the source code, which is what we already and have always done. So it doesn't apply. It doesn't require you use a particular license.

As you're so keen on searching our source you could have also easily read what the AGPL means, and seen that we use mutool^0, which I guess you would have done, if you were actually intending to be helpful rather than just trying to make us look bad, right? Hahaha! :)

I guess you're one of those people bitter at our success or maybe you were trying to use BrowserBox without paying the licensing fees and you didn't like that we made it commercial, is that right? Hahaha! :)

It seems if you were genuinely trying to be helpful rather than dishonest and trying to make us look bad, you would have just emailed me, right? Hahahahaha! :)

https://github.com/dosyago/chai/blob/37c1a1ec0941d81e0d6f8af...

If you're interested in this kind of thing, I packaged a lot of functionality (including zip files) into an open source doc viewer called "chai" (that also works on mac, install deps via brew).

Please note its focus is on security rather than looks so it converts docs to page images that you then view in (an optionally local) web client.

You can easily modify the convert process to move it to PDF rather than page images tho. Check it out: https://github.com/dosyago/chai