It is tedious to layout a PDF but actual pain points are handling variable sized images and amounts of text, try formatting recipes to a PDF... Your demo video explains the features but not how it can solve anything that is a major problem to me. The concept here in designing a template to be filled later is a brilliant idea, but I think its the delivery of the product that may pose the biggest problem. PDF generatio…
Thanks. Do you think by using an HTML template that can be filled in later is a better idea than visual designer?
Ask HN: Is PDF generation a real pain for developers?
21–30 of 31 posts
Re: Ask HN: Is PDF generation a real pain for developers?
#22Earlier quoted context omitted.
Thanks. Do you think by using an HTML template that can be filled in later is a better idea than visual designer?
The visual designer is great, it adds back in the ability for the designer to alter the template without the developer having to change any code. If this was a standalone product the template format would most likely need to be a proprietary format anyway for some basic piracy protection.
Re: Ask HN: Is PDF generation a real pain for developers?
#23Its a terribly painful. I have tried every single one of the options. I am still finding it extremely difficult to get it working. Once I managed to get it to print to pdf, then started the bigger problem 'Paging'. Paging is quite painful. I am writing my own code to split tables to fit into pages. If you can solve this problem. I would gladly pay.
We are looking into dynamic layout where tables can be split. It would be great to work along side you. Can I have your contact?
Re: Ask HN: Is PDF generation a real pain for developers?
#24It is tedious to code the layout and design of the PDF using code libraries such as FPDF, Prawn etc. I recently used Prince[1] to generate a PDF version of a web-based book. The PDF needed to be suitable for professional printing (crop marks, bleed, trim, etc.). Prince was the only solution I could find that came even close to being adequate for the job, and it exceeded my expectations. Creating the HTML for Prince w…
PrinceXML doesn't support a lot of the Html5 and CSS3. Canvas support doesnt exist, so I cant print charts.
Re: Ask HN: Is PDF generation a real pain for developers?
#25Re: Ask HN: Is PDF generation a real pain for developers?
#26Not amongst the kind of people who read HN. You might get some traction with semi-skilled PHP developers, but they rarely have much of a budget to work with and will generally use whatever is the cheapest acceptable solution.
This service would provide a good alternative, and regardless of what the developer is making, the price of the service would be far lower than paying the dev for the amount of time they spent futzing around with PDFs in PHP.
Re: Ask HN: Is PDF generation a real pain for developers?
#27Re: Ask HN: Is PDF generation a real pain for developers?
#28Earlier quoted context omitted.
Yes it will. Can we talk more about it?
So I could send it www.google.com and it would return a .pdf of google.com, exactly as it would look in the browser?
Re: Ask HN: Is PDF generation a real pain for developers?
#29Earlier quoted context omitted.
PrinceXML doesn't support a lot of the Html5 and CSS3. Canvas support doesnt exist, so I cant print charts.
I havent tried charts with princexml, but flying-saucer has capability to do custom rendering. So if you want, you can use a service to get image of your chart and then render that in the pdf as image.
Re: Ask HN: Is PDF generation a real pain for developers?
#30Earlier quoted context omitted.
So I could send it www.google.com and it would return a .pdf of google.com, exactly as it would look in the browser?
Sorry I must have misunderstood. That is what HTML2PDF engines do. We generate PDFs using our own templates.
HTML2PDFAAS, as I like to call it :)