171–180 of 191 posts
Congrats on the launch. I was a user of htmldocs back in the day, good to see more products in the space. One of the features I wish I had with htmldocs was the ability to automatically store generated documents in my own S3. I'd rather not introduce another cloud to my data stack just to host PDFs.
Earlier quoted context omitted.
I was looking at https://www.onedoclabs.com/pricing which says $0.005 per document, not page.
We indeed price starting at $0.005 per document, but have slightly updated the pricing following the good input we received yesterday from the community - hence the slight discrepancy in comments.
"Generate up to 1'500 documents per month without watermark"
1,500 instead of 1'500
Earlier quoted context omitted.
We indeed price starting at $0.005 per document, but have slightly updated the pricing following the good input we received yesterday from the community - hence the slight discrepancy in comments.
FYI there is a typo on the pricing page under the pro plan. "Generate up to 1'500 documents per month without watermark" 1,500 instead of 1'500
Earlier quoted context omitted.
Thanks! We try to make our product as accessible as possible for anyone to use (or at least to test). It's good to hear that our efforts have been worthwhile!
The text says "Instantly generate dynamic documents based on real-time data." but when I changed the react code to give the QR code a red color and clicked render it took far longer, maybe 5-6sec to render again.
The pricing is a little expensive. Have you heard of https://htmldocs.com/ I've been using them for a year now and it's free
This is definitely a somewhat painful process. I have done it with puppeteer / chromium on Debian, and it works very well after the headache of figuring it out. Having to pay 50 cents per PDF and deal with a 3rd party vendor would not provide value for our needs.
If I would want to put an image in footer on every page, would it reuse the same resource? How do you do shadows, spam rectangles or attach an image + mask, or maybe you bake that into the image itself? Many pdf tools are so bad at, the result can be even more than x10 in size and I don't even mean saving entire pages as JPEGs
I had to deal a lot with PDF generation over the past few years and I was very unhappy with the eco-system that was available: 1. HTML-to-PDF: The web has a great layout system that works well for dynamic content. So using that seems like a good idea. BUT it is not very efficient as a lot of these libraries simply spin up a headless browser or deal with virtual doms. 2. PDF Libraries (like jsPDF): They mostly just ha…
I'm with you.. We ended up writing a similar wrapper around https://github.com/jung-kurt/gofpdf library. We haven't open sourced it yet. But it's made it a lot easier to deal with rendering a PDF, especially over pagebreaks ect.
How is this better than writing out an HTML file, then using headless chrome to export to PDF, like this: "C:\Program Files\Google\Chrome\Application\chrome.exe" --headless --disable-gpu --print-to-pdf=C:\temp\foo.pdf --no-margins --print-to-pdf-no-header C:\temp\test.mhtml
This brings its own set of challenges. Headers and footers are strictly limited in terms of features, you cannot add footnotes, the notion of page spreads is harder to implement. Then you need to combine that with having a Chrome instance at hand + exposing the needed assets for URL resolution. Definitely not difficult let alone impossible, but not the easiest way to get started :)
Earlier quoted context omitted.
Curious, with ~$0.005 per document, what volumes do you do that pricing becomes a no-go for you?
In the long term, ~$0.005 per page (as opposed to document, which I assume hatchedlake meant) say on a mortgage document (~300 pages per) it adds up. The other alternative, which is to build this in-house (say 3 months and custom build, edge cases, such goodies), is more desirable (for us).